> I note that it’s AGPL. I think this is the same as fedora's tahrir < https://github.com/fedora-infra/tahrir/blob/develop/LICENSE>.
I think we just need to publicly fork this repo on ASF, in case the current fork dies or badgr changes model. > Are you suggesting that we use this service? I’m a little concerned about a free-to-use service, because there’s no protection against them suddenly changing that model when they realize we have *thousands* of users. Yes, see above ^ > Would probably be worth having a conversation with them about their available plans. This is a nice to have but probably not a blocker to start with initial badges, as long a public badgr fork exists. Perhaps it would make sense to check if the fork is deployable in case the self-hosting model is preferred in the future. > I think that work can happen in parallel to choosing a tool, so, sure, go ahead! I've thought a bit more and rather than starting with multiple badges, it probably makes more sense to start with a single badge to validate the idea. More can be proposed later if the first one is shown to be effective. I'd propose a pilot badge called 'My First Open Source Contribution' awarded to anyone first's contribution to an Apache project that opts-in to this badge. This recognition is straightforward to compute and would allow testing the program. We can recommend new/incubating projects to adopt the badge and it should be uncontroversial for existing projects to adopt the badge, since it helps with motivating first-time contributors. The badge image should be formatted to be easily repostable in socials (Linkedin and X initially) to allow awardees to share the badge and encourage more people to make first time contributions. On Thu, Feb 29, 2024 at 10:04 AM Rich Bowen <rbo...@rcbowen.com> wrote: > > > On Feb 29, 2024, at 9:44 AM, Paulo Motta <pa...@apache.org> wrote: > > > >> The most promising of these was Badgr (https://badgr.com/) which seems > to > > have become a paid service, and not open any more. > > > > An active fork of badgr is available on > > https://github.com/edubadges/edubadges-server. > > I note that it’s AGPL. Does that cause anyone concern? > > > > >> can someone step up to do the research to find one? > > > > I've played around with badgr.com a bit and was able to create the > > following organization and badge very quickly (the site usability is > pretty > > good): > > - ORG: https://badgr.com/public/issuers/bumbzeisQSuoN3Q_G4753Q/badges > > - BADGE: > > > https://badgr.com/public/assertions/ROzmBXUXQ9Cs86uMYdrGvA?identity__email=pauloricardomg%40gmail.com > > Cool. Thanks for digging deeper than I did. :) > > Are you suggesting that we use this service? I’m a little concerned about > a free-to-use service, because there’s no protection against them suddenly > changing that model when they realize we have *thousands* of users. Would > probably be worth having a conversation with them about their available > plans. > > > > > I've added more details about the fields required to create badges on > this > > comment: > > - > > > https://github.com/apache/comdev-working-groups/pull/26#issuecomment-1970310015 > > > > If moving forward with badgr make sense I can create a spreadsheet for > > folks to suggest badge types so we can get them set up. Then we can > > advertise to projects who can opt-in to the badging system. > > I think that work can happen in parallel to choosing a tool, so, sure, go > ahead! > > > > > > We could initially emit badges manually and later work on automating the > > process with stats from contribution feeds. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > >
