Re: [4diac-dev] Explorative prototypes for 4diac

[Martin Melik-Merkumians <Melik-Merkumians@xxxxxxxxxxxxxxxxx>]

Hi,

Sure, also non-committers should have this possibility if they find a sponsor/mentor committer, but still the committer would take the responsibility for maintenance in the end. That was more or less included in my mind 😊

Best,
Martin

-----Ursprüngliche Nachricht-----
Von: 4diac-dev-bounces@xxxxxxxxxxx <4diac-dev-bounces@xxxxxxxxxxx> Im Auftrag von Alois Zoitl
Gesendet: Donnerstag, 4. April 2019 17:17
An: 4diac developer discussions <4diac-dev@xxxxxxxxxxx>
Betreff: Re: [4diac-dev] Explorative prototypes for 4diac

Hi Martin,

I like this proposal a lot. This would give us more freedom to explore new ideas.

I would like to expand your proposal to allow also such feature branches for non committers. however in this case the potential contributor needs to find a committer supporting the idea and creating the feature branch for the contributor.

What do you think?

Alois


On Thu, 2019-04-04 at 15:03 +0000, Martin Melik-Merkumians wrote:
> 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
> http://www.acin.tuwien.ac.at/
> --------------------------------------------------
>
> _______________________________________________
> 4diac-dev mailing list
> 4diac-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or 
> unsubscribe from this list, visit 
> https://www.eclipse.org/mailman/listinfo/4diac-dev

_______________________________________________
4diac-dev mailing list
4diac-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/4diac-dev