Quick update:

   - My pull request for tearing down the Friend of Jenkins program on the 
   website was merged after the approval by the board members and comments in 
   this thread. Now https://www.jenkins.io/donate/#friend-of-jenkins points to 
   this thread
   - My estimation is that I would need 1 hour or so to update and open 
   source the Friend of Jenkins plugin, it is not a big deal. 
   - I added the discussion of the next steps to the next Jenkins 
   Governance meeting. If we agree on open sourcing the plugin and making it 
   downloadable from the update center, I am ready to take that action item
   
Best regards,
Oleg

On Wednesday, May 12, 2021 at 7:07:52 AM UTC+2 Oleg Nenashev wrote:

> Hi Zbynek! I was also thinking about a badges-alike approach in the 
> future. The Linux Foundation supports open badges on its platform, and we 
> could somehow get access to it. E.g. I have a badge for speaking at cdCon 
> there... IIUC it is based on https://info.credly.com/ .
>
> We could definitely explore it more if someone is interested. Badges for 
> financial donations are probably not the biggest use-case though.
>
> Best regards,
> Oleg Nenashev
>
> On Wed, May 12, 2021 at 1:29 AM Zbynek Konecny <[email protected]> wrote:
>
>> Hi,
>>
>> > recognizing donations through Jenkins social media
>>
>> sounds like a better approach than having a plugin. If there is a need to 
>> go beyond social media endorsements and invest time in a technical 
>> solution, I think instead of having some 2.0 version of the plugin one 
>> should look into the Open Badges standard and maybe issue different badges 
>> for financial support / coding / reviews / translations (see 
>> https://en.wikipedia.org/wiki/Mozilla_Open_Badges ). AFAIK such badges 
>> can be exported to LinkedIn and may get some attention there.
>>
>> Best regards,
>> Zbynek
>>
>>
>> On Tue, May 11, 2021 at 12:31 PM Oleg Nenashev <[email protected]> 
>> wrote:
>>
>>> > Honestly I'm not even sure it's worth spending the time to upgrade the 
>>> plugin. It just adds a low res icon and a link. I vote for discontinuing 
>>> the non distributed plugin. 
>>>
>>> There are some merits in the icon/link: pointing end users of Jenkins to 
>>> https://www.jenkins.io/participate/ . It **might** help to get more 
>>> visitors of this page and, hopefully, new contributors. 
>>> We could also discontinue the plugin and just include the functionality 
>>> into the Jenkins core. Should not be a big deal as long as it's opt-in in 
>>> appearance.
>>>
>>> BR, Oleg
>>>
>>> On Tuesday, May 11, 2021 at 3:19:21 AM UTC+2 [email protected] wrote:
>>>
>>>> Honestly I'm not even sure it's worth spending the time to upgrade the 
>>>> plugin. It just adds a low res icon and a link. I vote for discontinuing 
>>>> the non distributed plugin.
>>>>
>>>> On Mon., May 10, 2021, 11:34 a.m. Mark Waite, <[email protected]> 
>>>> wrote:
>>>>
>>>>> +1 from me on the proposal as well
>>>>>
>>>>> On Monday, May 10, 2021 at 5:20:02 AM UTC-6 [email protected] wrote:
>>>>>
>>>>>> +1 to proposal
>>>>>>
>>>>>> On Mon, 10 May 2021 at 11:08, Oleg Nenashev <[email protected]> 
>>>>>> wrote:
>>>>>>
>>>>>>> Would appreciate any feedback in this thread from the community
>>>>>>>
>>>>>>> On Wednesday, May 5, 2021 at 9:58:50 AM UTC+2 Oleg Nenashev wrote:
>>>>>>>
>>>>>>>> Dear all,
>>>>>>>>
>>>>>>>> We’ve recently had a few discussions with the board and Daniel Beck 
>>>>>>>> about the “Friend of Jenkins” plugin. This is a plugin referenced from 
>>>>>>>> https://www.jenkins.io/donate: *“In showing our appreciation, 
>>>>>>>> we’ll send out a special "friend of Jenkins" plugin to those who have 
>>>>>>>> donated at least 25 USD / 25 EUR. This plugin adds a little icon in 
>>>>>>>> the 
>>>>>>>> footer section, telling that you are a friend of Jenkins. You can 
>>>>>>>> install 
>>>>>>>> this to your Jenkins to show off that you’ve helped us”*. De 
>>>>>>>> facto, we have not been doing so in the recent years. There are a few 
>>>>>>>> problems associated with the plugin.
>>>>>>>>
>>>>>>>> *First of all*, you can become a “Friend of Jenkins” only by 
>>>>>>>> donating money. IMO it goes against open source values, we should 
>>>>>>>> equally 
>>>>>>>> appreciate all kinds of contributions and avoid promoting money 
>>>>>>>> donations 
>>>>>>>> specifically. *Secondly*, the plugin is private source at the 
>>>>>>>> moment. It is weird to send a private source plugin to anyone, 
>>>>>>>> especially 
>>>>>>>> as appreciation. *Thirdly*, the plugin is dated. It has not been 
>>>>>>>> updated for a while, and it does not use modern build/test pipelines. 
>>>>>>>> For 
>>>>>>>> example the code still targets Jenkins 1.396 as the build target. Even 
>>>>>>>> if 
>>>>>>>> the code is tiny, it is not good to send such a questionable build to 
>>>>>>>> Jenkins users and suggest its installation. *Last but not least*, 
>>>>>>>> sending private builds in email is flawed on its own due to the risk 
>>>>>>>> of 
>>>>>>>> various social engineering attacks.
>>>>>>>>
>>>>>>>> I suggest that we completely tear down the “Friend of Jenkins” 
>>>>>>>> program:
>>>>>>>>
>>>>>>>>    - We remove sections about “Friend of Jenkins” from the 
>>>>>>>>    Donations page
>>>>>>>>    - Instead of sending the plugin, the Jenkins Governance Board 
>>>>>>>>    will focus on sending appreciation letters and recognizing 
>>>>>>>> donations 
>>>>>>>>    through Jenkins social media. It should help us to build 
>>>>>>>> relationships with 
>>>>>>>>    donors and hopefully get them involved in the community.
>>>>>>>>    
>>>>>>>>
>>>>>>>> Later actions (no specific timeline):
>>>>>>>>
>>>>>>>>    - We (as community) open source the plugin as the standard 
>>>>>>>>    Jenkins plugin on https://github.com/jenkinsci, update it to 
>>>>>>>>    the modern development pipelines.
>>>>>>>>    - We update the plugin to reference 
>>>>>>>>    https://www.jenkins.io/participate/ instead of donations.  We 
>>>>>>>>    might add “Donate” as a type of participation to the list 
>>>>>>>>    - We release the plugin as 2.0, without changing the artifact 
>>>>>>>>    ID. Any user of the older private source version, if any, will be 
>>>>>>>> able to 
>>>>>>>>    update via the update center. Any Jenkins user will be also able to 
>>>>>>>> install 
>>>>>>>>    it via the plugin manager, no preconditions.
>>>>>>>>    - We reference the plugin from the install wizard suggestions 
>>>>>>>>    (not installed by default), and other places.
>>>>>>>>
>>>>>>>> There were also some discussions about building signed versions of 
>>>>>>>> the plugin and somehow allowing to verify the “Friend of Jenkins” 
>>>>>>>> status. 
>>>>>>>> Although I proposed it, now I do not think it is really needed. We can 
>>>>>>>> discuss it for future iterations.
>>>>>>>>
>>>>>>>> Would appreciate any feedback, and I suggest discussing that at the 
>>>>>>>> next Governance meeting.
>>>>>>>>
>>>>>>>> Best regards,
>>>>>>>> Oleg Nenashev
>>>>>>>> Jenkins Governance Board
>>>>>>>>
>>>>>>>> -- 
>>>>>>> You received this message because you are subscribed to the Google 
>>>>>>> Groups "Jenkins Developers" 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-dev/790a8d83-e939-4e96-adbe-98ca24f266dfn%40googlegroups.com
>>>>>>>  
>>>>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/790a8d83-e939-4e96-adbe-98ca24f266dfn%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>>>>> .
>>>>>>>
>>>>>> -- 
>>>>> You received this message because you are subscribed to the Google 
>>>>> Groups "Jenkins Developers" 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-dev/7ecbe41e-7882-4351-a346-4cb53ade8955n%40googlegroups.com
>>>>>  
>>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/7ecbe41e-7882-4351-a346-4cb53ade8955n%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>>> .
>>>>>
>>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "Jenkins Developers" 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-dev/d5a2f658-d7b6-49c5-9a27-14a8160384edn%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/jenkinsci-dev/d5a2f658-d7b6-49c5-9a27-14a8160384edn%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>> -- 
>>
> You received this message because you are subscribed to a topic in the 
>> Google Groups "Jenkins Developers" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/jenkinsci-dev/bIgDEM2E7hY/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> [email protected].
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/CABFvdGopS9p982PmW16ZHBZAaT3E0W6S44J08oFig36QQpCkPw%40mail.gmail.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-dev/CABFvdGopS9p982PmW16ZHBZAaT3E0W6S44J08oFig36QQpCkPw%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" 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-dev/64b06e78-cc4a-4385-be59-04a29e86deddn%40googlegroups.com.

Reply via email to