Hello again, A few weeks have passed so here's a re-cap of the information exchanged this far: 2010/3/9 Martin Paljak <mar...@paljak.pri.ee>: > Here are some plans that should make opensc-project.org more attractive to > both users and developers and also ease the administration burden. Lets > collect feedback for a week: please let me know which you feel would be > useful or what would absolutely resist. > > - Consolidate opensc-user and opensc-devel to maximize chances of response > and reduce confusion. Many questions that appear on opensc-user should either > have a FAQ entry (read below about faq) or are actually issues that will > require developer attention. Having a single opensc-devel would bring the > list of relevant mailing lists down to two (opensc-devel and muscle, many > people cross-post to both lists even now) Implementation tactics could be > directing people to opensc-devel only and asking existing subscribers > re-subscribe or do it automatically with an informational e-mail to > subscribers. Looking at subscriber lists reveals that about 1/3 of > subscribers on both lists follow the other list as well already.
Some people like it, some think that the audience of the lists is different. I don't have any strong feelings about it, eventually it should be also asked on opensc-user, what the subscribers there feel (as the idea would be to consolidate user list into devel, not vice versa). I still think that it could do good, but let it stay as it is for now. > - Have a clear path of communication: faq -> mailing list -> trac tickets. > With a single mailing list there is no question where to post and with a > single trac instance there is no question where to file bugs. Hopefully this > will re-animate trac tickets as a functioning issue tracking platform that > would benefit all parties. The "correct way of interaction" has been documented on https://www.opensc-project.org/opensc/wiki/GetStarted what should be the place where people look first (when they have no previous experience with OpenSC). The FAQ on the main page is still outdated but a skeleton for a new one is is online https://www.opensc-project.org/opensc/wiki/FrequentlyAskedQuestions The rest of the old FAQ (what really was more like a tutorial) must be merged with relevant developer or overview wiki pages (the information has been copied to relevant pages already) > > - Consolidate trac instances into a) a single OpenSC trac, moving all wiki > content and closing other trac-s b) closing all ticket sections in favor of > opensc trac but keep the wiki pages (and SVN browser) in read only mode. > Reason for this: Information is scattered between several trac-s, which all > require administration and housekeeping and is confusing to users as well. > None of the smaller trac-s have been actively used for ticket tracking or > have any other changes for months. This could be approached on a case-by-case > basis as well. No change in SVN repos. This was generally an accepted OK change, as information seems to be scattered and unorganized in the wikis. As a surprise a first ticket was posted to pkcs11-helper trac, asking for compilation help. Such requests should go to the mailing list instead, so maybe extending the "leave your e-mail" notice above new ticket entry could also include "and post to a mailing list if not sure" as well. I created a "namespace" for all wiki content of sub-projects (tagged as "project" in Trac) and copied the small content over. One exception is OpenCT, as it does not deal with PKCS#11, like the rest of projects. The copied wiki pages still need work and updating, but it should be done the OpenSC wiki, not the sub-wikis. I would turn the rest of the wikis read-only and add a to the rest of wiki templates a bold "this wiki has been moved to a new location: http://..."; and "please post new tickets to http:///...."; Everything will remain the same for the foreseeable future with timelines and svn browsers and svn addresses. > - Remove outdated static html content on opensc-project.org and replace > with/forward to the wiki. The fact that trac has been not used lately is due > to the registration being closed for a long period because of spam. Open > access to wiki and documentation (with a review for spam and such, of course) > will hopefully improve it. Fighting for spam is easy (or at least simpler) > now that necessary plugins are installed, but I installed them only to opensc > trac. This has been completed, all content has been moved to wiki. The generic cleanup done in the wiki (I already deleted some pages that were totally empty or 100% useless or outdated oneliners with dead links) and the current status of it is here: http://www.opensc-project.org/opensc/wiki/ProjectCleanup I've tagged most pages that need work with some (almost random) classification, either to signal that the page is old or should be improved or should be merged with some other page. > Most importantly, I would like to add a "this is what you should do" style > to the current "these are your options, try to figure it out yourself" > approach (so that people would not install *everything* they see on > opensc-project.org and then start to figure out what and why does not work > together.) This is a bit complicated as it is not easy to even suggest a card > with a reliable vendor and good support these days, as pointed out by > François Pérou. But something that should be done. > As a side product a new SSL certificate is installed on opensc-project.org, this hopefully does not scare away people who would like to work on Trac when they need to log in. I'd like to change the main page of opensc-project.org with what can be seen on http://www.opensc-project.org/opensc in near future, what do you think? > Ideas, feedback? The question still applies. Thanks for those who have voiced their opinions. Martin. _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
