Hello there!
I recently represented NeuroFedora at FOSDEM, and it was a great experience. I met many people from Fedora who knew about us, but also met a few who did not. I feel that at the very least, people from Fedora should know more about the group, our motivation, and what we do. We also seem to have a low number of contributors.
After my discussion with Sumantro, he recommended some steps to increase our community involvement within the Fedora community, which are summarised below:
1. Send out a call-for-participation to the -devel (or any other that may seem fit) mailing list (if we feel that we have a lack of contributor base), 2. More frequent blog posts (in the Fedora blogs or Fedora magazine) about the community. 3. Organize hackfests. Hackfests will attract more contributors. We can have packaging hackfests, where we spend straight hours packaging and reviewing software. A similar hackfest organized by the Badges community is present here[0]. 4. Talk to the Fedora Project Leader (Matthew Miller) about our sig and ask what we can do to increase the community outreach of our sig. Since he is the FPL, he can guide us more appropriately.
We can also have a brainstorming session as well on these points (in one of our future meetings) and discuss the forward direction of our sig.
[0]: https://fedoraproject.org/wiki/Badges_Hackfest_2020?rd=Badges_Hackfest_2019
On Tue, Feb 11, 2020 23:00:01 +0530, Aniket Pradhan wrote:
Hello there!
Heya,
Just replying here to summarise what we discussed in our call.
I recently represented NeuroFedora at FOSDEM, and it was a great experience. I met many people from Fedora who knew about us, but also met a few who did not. I feel that at the very least, people from Fedora should know more about the group, our motivation, and what we do. We also seem to have a low number of contributors.
After my discussion with Sumantro, he recommended some steps to increase our community involvement within the Fedora community, which are summarised below:
- Send out a call-for-participation to the -devel (or any other that
may seem fit) mailing list (if we feel that we have a lack of contributor base),
I do this by constantly posting review-swaps to the -devel list. Ideally, we should be packaging but swapping reviews with folks outside the neuro-sig. That way, we improve our links with the community.
So, let's try not to review each other's packages, and requesting review swaps on the -devel list instead.
- More frequent blog posts (in the Fedora blogs or Fedora magazine)
about the community.
We'll get back to these. Hopefully one every 2 weeks. A post on the neuroblog for our target audience, and also a post on the commblog for Fedora folks, if we can manage it.
- Organize hackfests. Hackfests will attract more contributors. We
can have packaging hackfests, where we spend straight hours packaging and reviewing software. A similar hackfest organized by the Badges community is present here[0].
Hackfests are a little more work. I don't think we have enough of a team to do this yet. Given how spread out we are over the world, even virtual hackfests are a challenge. Let's keep this on the list for when we have more resources?
- Talk to the Fedora Project Leader (Matthew Miller) about our sig
and ask what we can do to increase the community outreach of our sig. Since he is the FPL, he can guide us more appropriately.
Do we have specific things to discuss with them? Otherwise it won't be constructive. They have to look at all of Fedora, and they have to focus on the objectives that were set out. Maybe in the future when we have more resources, we could propose NeuroFedora or Fedora-Science as a community level objective. Then, the Council and FPL will be able to help us. At the moment, we're just another SIG.
https://docs.fedoraproject.org/en-US/project/objectives/
neurofedora@lists.fedoraproject.org