Hi<br><br><div class="gmail_quote">13. huhtikuuta 2012 22.57 Piotr Jawidzyk <span dir="ltr"><<a href="mailto:twilight312@gmail.com">twilight312@gmail.com</a>></span> kirjoitti:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
SD69, could You specify what You mean by "This is important stuff, and<br>
may move ahead in a way we don't like if we don't formulate a plan.",<br>
i.e. what's exactly a "bad way" we may experience?<br>
<br>
Generally, l see OBS thing with multiple targets (maintained by such<br>
experienced people as ones that proposed to lend a hand here) as a<br>
good thing - if it's going to work as "advertised". Yet, I can be not<br>
informed well, thus asking for clarification about possible caveats.<br>
<br></blockquote><div><br>it's a different beast so people will have to learn new tricks and adapt so I'd think the biggest problem might be the resistance to change. One big change visible to users would be that there wouldn't be a centralized devel repo anymore like extras-devel is. Altough there could be a project (repo) where people can push the hacky experimental stuff that isn't even meant for extras if needed. In general the devel stuff is in peoples home projects in OBS. For example my home project in the community obs looks like this <a href="https://build.pub.meego.com/project/show?project=home%3Atimoph">https://build.pub.meego.com/project/show?project=home%3Atimoph</a> Anyone can add the repo containing the stuff there to their device or copy/link the packages to their own projects. So if something is abandoned it's very easy to just copy the stuff and continue maintaining it. Dunno how the change is handled when promoting to extras though. Anyway, with OBS the whole thing is a lot more transparent so collaboration is easier with the packages. I can just post a link to my failed build's log and ask if I'm stupid or something.<br>
<br>I think the positive things outweight the negative things.<br><br>-Timo<br> </div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
> 've never seen such a statement from Nokia -- can you point to it?<br>
> Regards,<br>
> Jeremiah<br>
<br>
Unfortunately I can't, but SD69 got quotations + sources stacked.<br>
SD69, could You?<br>
<br>
/Estel<br>
<br>
2012/4/13, <a href="mailto:maemo-community-request@maemo.org">maemo-community-request@maemo.org</a><br>
<<a href="mailto:maemo-community-request@maemo.org">maemo-community-request@maemo.org</a>>:<br>
> Send maemo-community mailing list submissions to<br>
> <a href="mailto:maemo-community@maemo.org">maemo-community@maemo.org</a><br>
><br>
> To subscribe or unsubscribe via the World Wide Web, visit<br>
> <a href="https://lists.maemo.org/mailman/listinfo/maemo-community" target="_blank">https://lists.maemo.org/mailman/listinfo/maemo-community</a><br>
> or, via email, send a message with subject or body 'help' to<br>
> <a href="mailto:maemo-community-request@maemo.org">maemo-community-request@maemo.org</a><br>
><br>
> You can reach the person managing the list at<br>
> <a href="mailto:maemo-community-owner@maemo.org">maemo-community-owner@maemo.org</a><br>
><br>
> When replying, please edit your Subject line so it is more specific<br>
> than "Re: Contents of maemo-community digest..."<br>
><br>
_______________________________________________<br>
maemo-community mailing list<br>
<a href="mailto:maemo-community@maemo.org">maemo-community@maemo.org</a><br>
<a href="https://lists.maemo.org/mailman/listinfo/maemo-community" target="_blank">https://lists.maemo.org/mailman/listinfo/maemo-community</a><br>
</blockquote></div><br>