|
2009-08-15
, 07:35
|
Posts: 2,802 |
Thanked: 4,491 times |
Joined on Nov 2007
|
#12
|
The Following User Says Thank You to lma For This Useful Post: | ||
|
2009-08-15
, 08:33
|
|
Posts: 2,535 |
Thanked: 6,681 times |
Joined on Mar 2008
@ UK
|
#13
|
The Following 5 Users Say Thank You to Jaffa For This Useful Post: | ||
|
2009-08-15
, 09:45
|
Posts: 2,102 |
Thanked: 1,309 times |
Joined on Sep 2006
|
#14
|
That's never guaranteed, but IMHO the best indication would be source code being available under a Free Software/Open Source licence.
The Following 5 Users Say Thank You to lardman For This Useful Post: | ||
|
2009-08-15
, 15:46
|
|
Posts: 11,700 |
Thanked: 10,045 times |
Joined on Jun 2006
@ North Texas, USA
|
#15
|
That's never guaranteed, but IMHO the best indication would be source code being available under a Free Software/Open Source licence.
The Following User Says Thank You to Texrat For This Useful Post: | ||
|
2009-08-15
, 15:50
|
|
Posts: 11,700 |
Thanked: 10,045 times |
Joined on Jun 2006
@ North Texas, USA
|
#16
|
The other advantage of a Garage project is that the source code should remain available, even after a dev has moved on and perhaps removed their own public repo from wherever it was hosted. I think this continuity would be a good reason to ensure that projects do have a Garage project associated with them, even if the Garage SCM isn't used for day-to-day development and rather hosts snapshots.
|
2009-08-15
, 18:32
|
|
Posts: 2,669 |
Thanked: 2,555 times |
Joined on Apr 2007
|
#18
|
The Following 5 Users Say Thank You to zerojay For This Useful Post: | ||
|
2009-08-15
, 18:53
|
Posts: 2,802 |
Thanked: 4,491 times |
Joined on Nov 2007
|
#19
|
The other advantage of a Garage project is that the source code should remain available, even after a dev has moved on and perhaps removed their own public repo from wherever it was hosted.
|
2009-08-15
, 19:04
|
|
Posts: 11,700 |
Thanked: 10,045 times |
Joined on Jun 2006
@ North Texas, USA
|
#20
|
Certainly, both licence and code availability are important (see for example the ruby-hildon situation).
I wouldn't go as far as mandating (or even just offering incentives for) use of Garage as there are lots of valid reasons why developers may not want to use it. Besides, publishing in extras also ensures source code availability so isn't the push for extras enough to cover the disappearing developer case?
I see the best implementation of any sort of certification as orienting around App Manager. Something to inform users: "hey, THIS app is being well-managed so you have less to fear over possible abandonment". Such info should be available when previewing app info. Apps following this process could enjoy other benefits as well, such as prime rotation appearances in Downloads. Just a thought.
I'm not trying to step on any toes here or suggest draconian measures. Bottom line: how do we assure users that apps will likely be maintained, and how do we TRULY encourage coders to indulge? And if my questions are moot or foolish, hey, I can accept that.
Nokia Developer Champion
Different <> Wrong | Listen - Judgment = Progress | People + Trust = Success
My personal site: http://texrat.net