GNOME Bugzilla – Bug 463746
Content: Improvements to "Bring your project" page
Last modified: 2014-04-25 10:42:51 UTC
https://edit.gnome.jardigrec.eu/en/get-involved/bring-your-project is... ok, but there is still plenty of room for improvement: - All in all the page doesn't feel very exciting. There must be more and better reasons to bring your project to GNOME. Otherwise we wouldn't have all these excellent projects around. - Sounds to me like the message is addressed to someone already convinced. Let's fight more to convince the unconvinced. Look how many GTK+ based projects are out there and which percentage of them are willing to have a direct link to the GNOME project. - One missing point we should be selling is: when you bring your project to GNOME you are letting a community embrace you. Or something like that. You are not alone anymore, you will be able to create the channels of communication with other developers and power users that will probably test your software, provide feedback, file bugs, remind you guidelines and good practices, and so on. You will learn a lot and you will have a great context to show your greatness. - A very brief guide step-by-step would be interesting, linking to the pages describing the process in detail at lgo. - Here is also a good place to answer that known question: what should I do to get my software in the official GNOME release?
i could try once i'm back on broadband access
The link is not working anymore and after a quick search I couldn't find the page. Is this still relevant or can we close this as obsolete?
I can only guess as the link is down what's relevant and existing here: https://wiki.gnome.org/ReleasePlanning/ModuleProposing and https://wiki.gnome.org/ReleasePlanning/ModuleRequirements are the GNOME 2 (outdated) docs how to officially get a module included. This is obsolete now. http://wiki.gnome.org/MaintainersCorner is still relevant.