@guessed, is there such a page readily available?
http://code.mios.com/ could be a starting point, but i dont know who is administering that, is it open for users to add or MCV controlled?
Personally I like
code.mios.com as a centralized spot to download, document and otherwise "review" the complete history of a plugin, without going through tomes of Forums postings, and to provide a degree of consistency in the result.
The earlier parts, including the potential for rich/pictorial documentation and step-by-steps is important to folks who aren't tinkers, since the setup of the larger Plugins can be extensive. This latter part, to be able to see not only the final product, but it's
evolution and bug history/fix history is extremely important for Developers (we all learn by making huge mistakes
).
code.mios.com allowed the community to update the DSC Alarm code when that engineer left. Had that been a ZIP Attachment to a Forum thread, I would not have touched it with a TFP. It allowed folks, like @strangely and others, to contribute a ton to it's overall evolution... Similar things happened to the Phone plugin when it was exposed there, so we've already seen some of the benefits of clear ownership, over time, and community contribution.
I consider it a fairly good custodian/escrow location for code, instructions and downloads.
It's MCV owned/paid for, and accounts and source-control &/or wiki spaces are freely granted by PM'ing @mcvovidiu, which people can do once they exit
Newbie status (25+ posts gets you to
Sr. Newbie, which is enough to PM).
wiki.micasaverde.com is similarly controlled, but a bit more self-service to initiate, and have a background approval from MCV & Team to stop the spammers.
Anyhow, it's original purpose was to provide a
defacto spot for folks not wanting to host their own Source Control, Change-Log, Wiki, File storage etc, etc. It wasn't intended to be
the location, as we all have different ways of working, but it was there as a convenience, and to help provide a centralized catalog of techniques (by example) for those that want to contribute in that manner.
Not everyone is going to use it, so you can only
recommend places until the Marketplace is more concrete.
In the current state, I'd use the [pre-existing] Luup Projects wiki page as the jumping point. It already points to a number of the original plugins, categorized, and simply needs to be extended to include the newer ones that only exist in the Forums. I believe the documentation for those plugins, their dependancies (etc) should be put within their respective documentation/wiki/forum pages.
A Sticky, read-only, FAQ post at the top of this Board can point to
that page as the single "source of truth" for the existing Plugins. Over time, that post can be extended to include the other FAQ items that routinely come up... either as direct content, or more likely as pointers to the SoT Posting on the matter.
