![]() |
Re: maemo.org website clarity & organization
Hi rotoflex,
Quote:
A "blocker" is "a bug which blocks the package from being promoted to Extras" - as such, only serious problems should block packages. These problems should cover filesystem corruption & systemic overuse, excessive power consumption in normal operation, legal issues, lack of a community reporting mechanism, and any non-edge-case crasher bugs. I personally disagree with the "blocker" list on 2 points: not all crashers or incomplete features should be blockers, IMHO - if an application crashes when some unusual set of circumstances happens, then it should still get promoted; and I don't think we should be policing "missing announced features". So if you would like to update the lead-in paragraph to elaborate on what is meant by a blocker, then I would be delighted! Just log in, click on the edit link beside the paragraph, and update. Everything is version controlled, so you have a safety net to roll back if you are unhappy with the result. Good luck! Dave. |
Re: maemo.org website clarity & organization
Hi,
Quote:
First stop: our getting started in the wiki page, linked to whenever you edit a page: http://wiki.maemo.org/Contributing_to_the_wiki You have a simple but multi-step process to follow to get on the first step:
You can also edit the wiki anonymously, if you know how to do simple additions. I hope this helps you get started! Cheers, Dave. |
Re: maemo.org website clarity & organization
Quote:
|
Re: maemo.org website clarity & organization
Quote:
Agreed. Just pointing out that I don't agree with all the things we consider blockers (and am on the record as saying that the extras-testing process places too much of a burden on app developers & packagers). Just my opinion, of course. Dave. |
All times are GMT. The time now is 20:18. |
vBulletin® Version 3.8.8