ah GCDS... Getting GNOME Do into GNOME superficially sounds like a fantastic and fun idea. I think there is a lot to be gained by being inside of GNOME. However, like you, I see the baggage this brings along as a little too much. Moving our bug tracker, source code, release policies, and website, while sucky, are only secondary blockers to me. The big one to me is the "extra work commitments", which provide an additional burden I do not think our dev team can handle in its current condition. We have 5 core members, all of whom have what can be only described as a part-time commitment to GNOME Do when at any time any of us may be required to walk away for an extended period of time.
What I am getting at here is I think we do best when we have the freedom to work when we can on what we can, and not have additional upstream requirements on our work times. Ultimately, I think being forced to work on tools not of our choice means we will be slowed down further. For these poorly stated and quickly typed reasons, I think we should stay outside of GNOME. Jason On Mon, 2009-07-06 at 16:27 +0100, David Siegel wrote: > A lot of people at Gran Canaria Desktop Summit are asking about > getting Do into GNOME, and I am having trouble seeing the benefit for > us. Switching to Git/GNOME infrastructure strikes me as a step in the > wrong direction, but people are interested so I thought I would share > this with the list to see if anyone has thoughts. > > http://live.gnome.org/ReleasePlanning/ModuleProposing > > Here is my understanding of the situation: for the last ten years, > GNOME made all of its own applications. In recent years, independent > application authors emerged from the GNOME community, developing > applications on their own but with the intent of eventually getting > them into GNOME. When I started Do, I just wanted to create a great > free software application that was fun, exciting to hack, and > incredibly useful. Together we have built an incredible project, with > hundreds of thousands of active users, awesome contributors, excellent > development and design practices, distro adoption, and vision. When > people started suggesting GNOME inclusion, I said "GNOME can do > whatever it wants, just like the distros -- if they want to include > Do, go for it." Then I was told that inclusion in GNOME would put > extra work commitments on us, and put extra constraints on details > like where we host our website and wiki, where our source lives, how > we handle bugs and translations, etc. I am all for GNOME inclusion, > but I think our project should operate completely independently of the > GNOME project, not be absorbed by it. As far as I can tell, our > project doesn't need GNOME oversight, endorsement, or infrastructure. > If extra work needs to be done for GNOME inclusion, GNOME contributors > should do that work. > > Thoughts? > > David > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "GNOME Do" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/gnome-do?hl=en -~----------~----~----~----~------~----~------~--~---
