ispo-working-group
ispo-working-group copied to clipboard
InnerSourceCommons
Bazaar plugin updates for README/Contributing visibility
MVP is launched! Need to contribute to Backstage core before contributing back to Bazaar.
https://drive.google.com/file/d/1hVKCofRzMakBZT56qdcH36NqW6gLliP8/view?usp=drive_link https://drive.google.com/file/d/1UKrLUgdggnkM4Jd3MUYzrCHvkjIhLDX8/view?usp=drive_link
Screenshots of the customised dashboard and the project details on each card. This is the MVP, next phase will include:
- Project Programming Languages
- Automation ( pulling information directly from README file.
- Adding project score/ranking
Found out BackStage next Office Hours times are as follows, will try to participate if possible with our developer to learn about the latest of Bazaar:
Hello @azinshahidi2019 , did had the chance to participate on any of the office hours? Anything to report back?
We weren't able to join the intended office hour on 7th of December. Based on our recent research, contributing back to BackStage and Bazaar is close to impossible due to the internal customisation by our team for BackStage. We have repurposed BackStage attributes for Bazaar based on our needs and used internal APIs to pull in Programming languages. We have change the fields names to Trusted Committers and Maintainers and expecting to populate those directly from our Readme and Contributing files. Otherwise manually add them to the project creation form. All in all, customisation is a barrier for contributing back, however, we can at some point share all our customisations with BackStage guys as suggestions and they improve their dashboard if they like.
OK thanks for letting us know. Bummer to be on your own internal fork, now, but it would be neat to see sometime your learnings.
@azinshahidi2019 we would love to hear (for the learning of our community) what are the blockers to contributing back and what are the features that you developed?
As part of the onboarding work, We've implemented a few rules to test for and extract required info, which could be used to grade projects based on our InnerSource expectations. We've initially organised the rules into 'Bronze', 'Silver' and 'Gold' and we've attached the report to each project, this could be used to help highlight the most compliant projects or to help project owners to view where the system is pulling data from. These grading flags also appear in their colours on the Bazaar dashboard cards.
That’s awesome! What are the rules? Would you be open to demoing your work and approach sometime in and #ispo-working-group meeting?
Oh, I attached the screenshot but seems like company security hasn't let it to attach. I will attached the screenshot from home later byt till then here are the rules:
Bronze: Has REDME.md file and Has CONTRIBUTING.md file or Has a Contributing Section
Silver: Has Project Name and Has Project Description and Has Usage (or Getting Started) Section and Has a Installation (or Environments) Section
Gold: Has Communication Link and Has Issues Link and Has Members Roles And Has Governance.md file or Has a Governance Section
@rrrutledge for demoing, I should get permission from our legal team. But please give us a few months to figure it out. As you know, these type of activities are very complicated with Financial companies.