Created Fri, 23 Mar 2012 14:12:15 +0000 by Addidis
Fri, 23 Mar 2012 14:12:15 +0000
While we have the chipkit wiki which has a library status page it seems behind (specifically the ethernet is what I noticed. It does not reference the working one on the networkshield product page by Rick.)
We also have a Libraries forum above this, which imho appears to be for finished functioning libs that are written / tested for chipkit. It has some requests, and other things that force you to sift threw the posts to get to what most people are looking for there. Libraries to slap in and play with.
Problem: No clear place to find all tested working libs with exceptional signal to noise ratio. & Requests are probably not seen given the considerable dilution of the request's by actual libs.
Solution: Create a lib request forum. The one by the software releases up top of the index should be noted to be for actual libraries(beta+) and the requests should be done in the request section. This enhances the signal to noise ratio for both users. Those asking for help with creating libs, and those looking for libs to work now. Also for those who are looking for things to port based on a proven "need" for it. One person posts the request, more second it, some one looking for a project knows what to port by the popularity of the post. If you like the lib that is posted you can include it and its examples in the IDE or how ever you decide to show official acknowledgment of the lib. Perhaps just sticky it in the forum.
Also you should consider appointing community mods. The spam problem and the inability for new users to post links is not a trivial handicap. The key to solving the problem is 2 part. Allow reporting of posts and appoint community mods to resolve them. The volume of spam makes it unrealistic to combat unless you have community help. Not allowing new users to post links is a serious handicap.
Sat, 24 Mar 2012 05:40:33 +0000
Also you should consider appointing community mods. The spam problem and the inability for new users to post links is not a trivial handicap. The key to solving the problem is 2 part. Allow reporting of posts and appoint community mods to resolve them. The volume of spam makes it unrealistic to combat unless you have community help. Not allowing new users to post links is a serious handicap.
I like the idea of appointing community moderators, I would be happy to delete spam so others don't have to read it and I would be even happier if someone else deleted it so that I didn't have to read it.
I agree the library issue is confusing. I think the best place to look for a quick status is the wiki. I've added a disclaimer at the top of the wiki lib status page so that people reading it will know that the listed status may lag the actual code.
I also see that someone is adding a release version to the status... This should help.
Jacob