| [4diac-dev] Explorative prototypes for 4diac |
|
Hi all, I (and probably you too) often develop explorative prototypes. Unfortunately, currently options for feedback is limited, as there is no possibility to publish them easily over the 4diac repositories to make them available
to a larger audience. I also understand that it is impractical to publish them onto the mainline development via the version branches or the development branch, as they will usually involve major modifications on the model, infrastructure
or whatever else, and are always prone to be abandoned or deemed not worth the hassle. Therefore I would like to propose, that if such a prototype shall be made public available, committers should be able and allowed to publish separate feature branches, marking
them with their CommiterName and taking full responsibility for maintaining the branch. At some time in the lifecycle of such a branch and if the original committer desires it, a public vote can be performed if such a branch shall be carried over into the mainline development. If such a public vote is inconclusive,
a committers vote shall then be performed. I think with this rules, we can safely deploy our ideas and prototypes for 4diac and the future of IEC 61499 into the public, get user feedback for the development phase, and the users’ decision at the end if the proposed
feature is worth the hassle. What’s your opinion on my proposal? Best regards, Martin -------------------------------------------------- Dipl.-Ing. Martin Melik-Merkumians Advanced Mechatronic Systems Automation and Control Institute (ACIN) Vienna University of Technology DVR-Number: 0005886 Gusshausstr. 27-29, room CA-05-38 1040 Vienna, Austria Phone: +43 (0)1 588 01 37688 Fax: +43 (0)1 588 01 937688 Email:
melik-merkumians@xxxxxxxxxxxxxxxxx -------------------------------------------------- |