Hello, I saw some discussion about adding new features to Padre on IRC.
Padre is of course not complete yet, but it seems now to be in a state where at least some people would like to have rather stable releases, which may end up being packaged for Linux distributions etc. So it is quite natural to be a bit more conservative about adding new and possibly incomplete features, because they could somehow damage the appearance of Padre as a stable product. Of course, nobody should be prevented from developing new features for Padre, nor should users be prevented from using them if they want. So here is my suggestion: If possible (from an architecture point of view), develop a feature first in a plug-in. If the feature turns out to work nicely, makes sense as a core feature, and has matured a bit, we can move it to the Padre core. Of course, people need to know about such features so that they can try them out. Here I see two possible solutions: 1. Authors of new features advertise their plugins, and it would be nice to even mention the experimental feature plugins in Padre release announcements and in the Padre docs. 2. There is no need for creating a new plugin for each feature, so possibly a plugin called Padre::Plugin::ExperimentalFeatures (or whatever nice name you come up with) would suffice. What do you think? Best regards, Zeno -- MyMediaLite Recommender System Library: http://ismll.de/mymedialite _______________________________________________ Padre-dev mailing list Padre-dev@perlide.org http://mail.perlide.org/mailman/listinfo/padre-dev
