#442 Licensed to Push - Get added as a contributor to Pagure repositories
Closed: declined 2 months ago by riecatnor. Opened 3 years ago by jflory7.

= Badge Description =

  • '''Name''': Licensed to Push {I,II,III,IV}
  • '''Description''':
  • I: Congratulations, you were added as a contributor to your first repository on Fedora Pagure (pagure.io)!
  • II: You've been added as a contributor to 10 repositories on Fedora Pagure (pagure.io).
  • III: You've been added as a contributor to 25 repositories on Fedora Pagure (pagure.io).
  • IV: You've been added as a contributor to 100 repositories on Fedora Pagure (pagure.io). With great power comes great responsibility...

= Understanding badge =

1) What are those activities?

  • '''Users are granted badge for being added as a contributor to a respository on Pagure, Fedora's git hosting service'''

2) Who is doing them (are they packagers? translators? newcomers? veterans? users? sponsors?)

  • '''Packagers, developers, maintainers, etc.'''

3) Why are they doing them (is this a means to a different end?)

  • '''Adding more contributors to a repo to help with development of a project (usually as a permanent member of the project / repo)'''

4) When do they do them (every day? once a year?)

  • '''Once per repository (although a user could be removed and added to the same repo again, should be taken into consideration)'''

5) How do they do them (by talking in IRC? by running commands in the console? by using a web interface?)

  • '''Another repository admin / owner is adding them as a contributor'''

= Artwork concepts =

  • <optimistic>In spirit of the badge name and its [http://ecx.images-amazon.com/images/I/51j-SggaWSL.jpg inspiration], some sort of snap of the tail end of a plane with a number for the repositories added to (e.g. 1, 10, 25, 100)</optimistic>
  • {Panda,badger} standing, holding a rectangular-shaped card (like a licenseā€¦) with the number of repositories they are added to on it
  • Some kind of combination of keys (e.g. Crypto Panda / Badger) mixed with Pagure logo

= Other discussion =

As of the moment, I don't know if there is a fedmsg hook in place to automate this badge series. If there is, this ticket's concept can be marked as "approved". If not, this ticket should be closed and the badge definition status set to "not yet possible".

Note, this ticket is similar to #434.

I am CCing robyduck and pingou to help advise on this one in terms of whether it is possible.


Yes there is a fedmsg, I uploaded the yml file to ticket #434, just for the first badge but all others are similar. See https://fedorahosted.org/fedora-badges/attachment/ticket/434/long-life-to-pagure-01.yml

Yes there is a fedmsg, I uploaded the yml file to ticket #434, just for the first badge but all others are similar. See https://fedorahosted.org/fedora-badges/attachment/ticket/434/long-life-to-pagure-01.yml

Thanks for confirming, robyduck!

Thanks for confirming, robyduck!

Hi! I've made some concepts of the badges, based off of your <optimistic> suggestion </optimistic>.
[[Image(http://i.imgur.com/nnk3nRp.png)]]
[[Image(http://i.imgur.com/RKDOJu0.png)]]
[[Image(http://i.imgur.com/YPziYlT.png)]]
[[Image(http://i.imgur.com/QqNm5nF.png)]]

Hi! I've made some concepts of the badges, based off of your <optimistic> suggestion </optimistic>.
[[Image(http://i.imgur.com/nnk3nRp.png)]]
[[Image(http://i.imgur.com/RKDOJu0.png)]]
[[Image(http://i.imgur.com/YPziYlT.png)]]
[[Image(http://i.imgur.com/QqNm5nF.png)]]

Replying to [comment:3 hegataro]:

Hi! I've made some concepts of the badges, based off of your <optimistic> suggestion </optimistic>.

Wow, these look awesome!! Thanks so much for tackling these, hegataro. I'm CCing a few more Design Team members to take a look, and maybe we can move forward on pushing this badge out. :)

Replying to [comment:3 hegataro]:

Hi! I've made some concepts of the badges, based off of your <optimistic> suggestion </optimistic>.

Wow, these look awesome!! Thanks so much for tackling these, hegataro. I'm CCing a few more Design Team members to take a look, and maybe we can move forward on pushing this badge out. :)

I'm still thinking this badge just replies what we have in ticket 434. Being added to as many repos as possible is not really a measurement of contributing. Doing stuff to one or more repos, committing changes and pushing them out is what we should get here IMHO (which is ticket 434, I would not make two series for the same thing).

I'm still thinking this badge just replies what we have in ticket 434. Being added to as many repos as possible is not really a measurement of contributing. Doing stuff to one or more repos, committing changes and pushing them out is what we should get here IMHO (which is ticket 434, I would not make two series for the same thing).

Replying to [comment:5 robyduck]:

I'm still thinking this badge just replies what we have in ticket 434. Being added to as many repos as possible is not really a measurement of contributing. Doing stuff to one or more repos, committing changes and pushing them out is what we should get here IMHO (which is ticket 434, I would not make two series for the same thing).

The idea behind this proposal is that it's supposed to fit into an on-boarding series for teams like Fedora Infrastructure especially (and other development-oriented SIGs) to help document the steps for newcomers to get involved. Their progress would be marked with badges as they progress in the levels of contributing.

While you can commit as much as you want to any given Pagure repo(s), being added to other repositories encourages developers to reach out to other projects, find ways to contribute, and after making meaningful contributions, they could be added to another repository. There is a possibility for the commits badge to be awarded for inward contributions (e.g. you are working on a personal project in Pagure), but I believe this one holds its merit as a concept and an idea because it's encouraging people to explore Pagure, find projects that interest them, and make contributions in places they might not have known existed prior.

I'm still +1 to seeing both proposals for #434 and this one become their own series.

Replying to [comment:5 robyduck]:

I'm still thinking this badge just replies what we have in ticket 434. Being added to as many repos as possible is not really a measurement of contributing. Doing stuff to one or more repos, committing changes and pushing them out is what we should get here IMHO (which is ticket 434, I would not make two series for the same thing).

The idea behind this proposal is that it's supposed to fit into an on-boarding series for teams like Fedora Infrastructure especially (and other development-oriented SIGs) to help document the steps for newcomers to get involved. Their progress would be marked with badges as they progress in the levels of contributing.

While you can commit as much as you want to any given Pagure repo(s), being added to other repositories encourages developers to reach out to other projects, find ways to contribute, and after making meaningful contributions, they could be added to another repository. There is a possibility for the commits badge to be awarded for inward contributions (e.g. you are working on a personal project in Pagure), but I believe this one holds its merit as a concept and an idea because it's encouraging people to explore Pagure, find projects that interest them, and make contributions in places they might not have known existed prior.

I'm still +1 to seeing both proposals for #434 and this one become their own series.

Hey hegataro! Great work! One little thing: let's make the outlines thicker to make the graphics stand out. This badge can be an inspiration:
[[Image(https://badges.fedoraproject.org/pngs/pkgdb-partners-in-crime.png)]]

Also please check the background color in the badge guidelines, we want to keep them consistent.

Heya! I've thickened the outlines and made the background color more in-tune with the guidelines
[[Image(http://i.imgur.com/N3FGw8Z.png)]]
[[Image(http://i.imgur.com/toibLLZ.png)]]
[[Image(http://i.imgur.com/bHpFnkR.png)]]
[[Image(http://i.imgur.com/pJ3RjO2.png)]]

Heya! I've thickened the outlines and made the background color more in-tune with the guidelines
[[Image(http://i.imgur.com/N3FGw8Z.png)]]
[[Image(http://i.imgur.com/toibLLZ.png)]]
[[Image(http://i.imgur.com/bHpFnkR.png)]]
[[Image(http://i.imgur.com/pJ3RjO2.png)]]

For what it's worth, I think this artwork is priceless. :)

For what it's worth, I think this artwork is priceless. :)

What is the title of the badge referencing? I'm not sure I follow the reference. Either way, from the image you have uploaded I do not think that the artwork proposed is translating to the tail end of a jet.

What is the title of the badge referencing? I'm not sure I follow the reference. Either way, from the image you have uploaded I do not think that the artwork proposed is translating to the tail end of a jet.

Ah, ok, it is referencing the Beastie Boys album.. Unfortunately, I still don't think the artwork is translating well. And I am not sure that this reference will come across for a lot of folks. Perhaps we should try another concept for the artwork.

I like the second concept for this one, could be straight forward and allow for a nice series. Would be nice to have the Pagure logo on the card :)

Ah, ok, it is referencing the Beastie Boys album.. Unfortunately, I still don't think the artwork is translating well. And I am not sure that this reference will come across for a lot of folks. Perhaps we should try another concept for the artwork.

I like the second concept for this one, could be straight forward and allow for a nice series. Would be nice to have the Pagure logo on the card :)

Metadata Update from @jflory7:
- Issue assigned to hegataro

2 years ago

Metadata Update from @riecatnor:
- Custom field artwork adjusted to None
- Custom field concept_review_passed adjusted to None (was: 1)
- Custom field has_complete_yaml reset (from None)
- Custom field has_description adjusted to on (was: 1)
- Custom field has_name adjusted to on (was: 1)
- Custom field needs_manual_award reset (from 0)
- Custom field triaged adjusted to on (was: 1)
- Issue close_status updated to: None
- Issue tagged with: artwork-intermediate, artwork-needed, development

2 years ago

Metadata Update from @riecatnor:
- Custom field artwork adjusted to needed (was: None)
- Custom field has_complete_yaml reset (from false)
- Custom field needs_manual_award reset (from false)

2 years ago

@skamath Could you confirm that these badge rules are still up to date?

Metadata Update from @jflory7:
- Custom field has_complete_yaml reset (from false)
- Custom field needs_manual_award reset (from false)

2 years ago

The yml looks good to me :)

Closing this ticket due to inactivity during Badges virtual hackfest. Please reopen if their is renewed interest. Thanks!

Metadata Update from @riecatnor:
- Custom field has_complete_yaml reset (from false)
- Custom field needs_manual_award reset (from false)
- Issue close_status updated to: declined
- Issue status updated to: Closed (was: Open)

2 months ago

Login to comment on this ticket.

Metadata
Attachments 8
Attached 3 years ago View Comment
Attached 3 years ago View Comment
Attached 3 years ago View Comment
Attached 3 years ago View Comment
Attached 3 years ago View Comment
Attached 3 years ago View Comment
Attached 3 years ago View Comment
Attached 3 years ago View Comment