Hi, The best way to go forward on that one would be to add that item as a subject for the next Gov meeting (caveat, in almost a month since next one is skipped because of Jenkins World): https://wiki.jenkins-ci.org/display/JENKINS/Governance+Meeting+Agenda
And then, Ioannis, attend the meeting on IRC (#jenkins-meeting). Depending on your TZ, it can be more or less difficult. But if I'm not wrong, that should be in your afternoon, so probably possible. Cheers 2016-09-01 17:52 GMT+02:00 'Björn Pedersen' via Jenkins Users < [email protected]>: > For details probably check : > https://wiki.jenkins-ci.org/display/JENKINS/Governance+ > Document#GovernanceDocument-Trademark > > > Am Donnerstag, 1. September 2016 16:37:35 UTC+2 schrieb Andrew Bayer: >> >> I believe this needs board approval. >> >> A. >> >> On Thu, Sep 1, 2016 at 7:25 AM, Ioannis Moutsatsos <[email protected]> >> wrote: >> >>> Greetings to all; >>> >>> We have developed a number of scientific applications based on >>> Jenkins-CI. Essentially we are able to deliver scientific workflows and >>> data pipelining using the Jenkin-CI framework and selected ecosystem >>> plugins. Much of the philosophy and strategy has been presented as part of >>> the BioUno <http://biouno.org>open source project. >>> >>> Now, I would like to open source the know how, Jenkins jobs and >>> utilities that support high performance scientific imaging that I have >>> developed for the company I work for. The public Git project will accompany >>> a manuscript we have submitted for publication. >>> >>> My question (as a non lawyer and scientist) is whether there are any >>> restrictions or preferences on the use of the 'Jenkins' name. Internally we >>> refer to our project as *Jenkins for Life Sciences Continuous >>> Integration* or Jenkins-LSCI. Would this be an acceptable name to >>> publish the project on GitHub or are we running into legal issues and >>> objections here. >>> >>> Any feedback or previous experiences is welcomed. >>> >>> Thank you >>> Ioanns >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Jenkins Users" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> To view this discussion on the web visit https://groups.google.com/d/ms >>> gid/jenkinsci-users/43bd083e-6e54-4c7b-867b-047dde98b1c6% >>> 40googlegroups.com >>> <https://groups.google.com/d/msgid/jenkinsci-users/43bd083e-6e54-4c7b-867b-047dde98b1c6%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/jenkinsci-users/fae0080f-8bb8-4f63-96ca-d47f68a37b90%40googlegroups. > com > <https://groups.google.com/d/msgid/jenkinsci-users/fae0080f-8bb8-4f63-96ca-d47f68a37b90%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS511Zx233fBgE4Rqdqq8638FY0QuMirf1qXU5GPRq17Uw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
