--
You received this message because you are subscribed to the Google Groups "SilverStripe Core Development" group.
To post to this group, send email to silverst...@googlegroups.com.
To unsubscribe from this group, send email to silverstripe-d...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/silverstripe-dev?hl=en.
Would be good to also get a column for dependencies as this is going to be a rather important part of the API i.e (recaptcha requires the spam protection module) some of UncleCheese's upload files require other things... As SS gets bigger the dependancies will get larger.c. - If you build the API on top of restful server you can get quite a bit of functionality out of the box :D (json, xml support, caching, RESTful interface).
How did you get that list? by hand? If you want I can dump the ss.org module information to csv if you wish.
One of the things I also want to include is a system to check if the module "code" has already been used... so we can avoid two modules with the same name.
--
Yes, the code to me is like the directory name when installing in the silver-stripe folder and should be unique -but doesn't have to be the same as the module name.ie 'DataObject Manager' is dataobject_manager etc
--
Some example criteria:
- has test suite
- tests pass
- test coverage is close to 100%
- documented well
- uses perscribed README format
- sapphiredocs user/dev documentation
And perhaps some other useful stats (like ohloh.net provides):
- when module was last updated
- activity level
- lines of code
- "I use this module" (can help determine popularity)
- rss feeds
- related modules
Another thing I think we need to figure out is how to encourage
participation on modules. There are currently some modules that I'm sure
people have improved upon, but none of this code actually shows up on
the module page for others to take advantage of.
Also if the original maintainer abandons the module, we don't have a way
of getting someone else to take over it, or to see the improvements get
added in.
Perhaps the mainter(s) get a reminder email once a year, where they opt
to continue being the maintainer, otherwise they are automatically
disconnected from it, and others can opt to become the maintainer if
they like.
Thoughts?
--
You received this message because you are subscribed to the Google Groups "SilverStripe Core Development" group.
To post to this group, send email to silverst...@googlegroups.com.
To unsubscribe from this group, send email to silverstripe-d...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/silverstripe-dev?hl=en.
--
You received this message because you are subscribed to the Google Groups "SilverStripe Core Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to silverstripe-d...@googlegroups.com.
To post to this group, send email to silverst...@googlegroups.com.
Visit this group at http://groups.google.com/group/silverstripe-dev.
For more options, visit https://groups.google.com/groups/opt_out.
Hi All,
Another aspect to consider is the quality of the documentation. With users varying in skill level implementing/using a module can severely be affected by the quality of the documentation. You could have a well coded module, that does what it is supposed to, but because you don't know what the intent/function is due to poor documentation it hampers the use of the module.
Shaun
--
You received this message because you are subscribed to the Google Groups "SilverStripe Core Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to silverstripe-d...@googlegroups.com.
To post to this group, send email to silverst...@googlegroups.com.