On Sun, Feb 02, 2020 19:46:30 -0000, Erich Eickmeyer wrote:
> On Fri, Jan 31, 2020 17:30:34 -0000, Erich Eickmeyer wrote:
> I don't know enough about the Jam. Were they using an FAS group to
> manage things, like packages, for example? I couldn't find an "audio"
> "jam" FAS group when I looked.
Same, I couldn't find one either.
Ah---maybe you can create one if a team is going to maintain packages.
But this can be done later (packager FAS groups are explained later in
> If you can tell us your FAS username, I can add you to the
> group in the meantime so you can edit pages there.
My FAS username is "eeickmeyer". :)
I've added you to the wikiedit group now. You should be able to edit the
> The packaging SIG has a very well defined process---the idea is
> ensure that package maintainers are aware of their duties and the skills
> they need:
> Again, quite a few sponsors around, so if you take over the maintenance
> of the Fedora Jam SIG and its packages, there should be no trouble
> sponsoring you as a package maintainer too :)
Yes, I've been looking at that. Since I'll be introducing one or two
new packages that I know of off the top of my head, it just seems to
be a logical choice for somewhere to go. One of those packages isn't
quite ready (I want to go with whatever we release into Ubuntu), so
I'm waiting on that. Additionally, we plan on moving that package from
Launchpad's git system to github so that we can de-ubuntuize it, for
lack of a better term. :)
That sounds great. I've seen your e-mail to the -devel list too. So, I
don't think packaging will pose much issue.
> I don't see an FAS group associated with this either, somehow.
I believe that's the "packaging" group, pretty simply. I saw it in the
list. Seems to be a prerequisite for joining a lot of other groups.
Yes---there are two general types of groups on FAS:
"Tracking" groups are merely to keep track of members---usually they
don't give a member any extra permissions.
The "Packager" group is sort of a base group that a gives access to our
packages. Well, the ones a member maintains. (To be able to work with
all packages, even ones that are maintained by others, one has to be a
Other "packager" groups are generally used to share packaging
responsibilities. For example, we have the neuro-sig packager group.
Everyone in this packager group can commit to all packages maintained by
this group. One has to be in the packager group to be able to join other
packager type groups.
I don't see a packager group related to the Jam, so you could request
for one to be able to similarly share packaging responsibilities if you
think that would help. (It really does help us in the neuro-sig)
> So, in general, a SIG is just a bunch of people working on something
> together. A SIG may not always have an associated FAS group---it depends
> on what the SIG's requirements are.
> I also saw your post on Telegram about the #fedora-jam IRC channel. I
> think @jflory gave you a link on the process already. However, I noticed
> that the Jam seems to have a channel already: #fedora-audio
I'll join the #fedora-audio channel, but if it's dead with just
lurkers, I'd rather start with something new.
Sure! Makes sense.
> Do you think this can either be reused, or if not, the documentation
> updated so your users know? (There also seems to be a mailing list.)
Let me put it this way: there's a ton of outdated documentation
Ubuntu's wiki regarding Ubuntu Studio that I haven't even touched
because it's that poorly outdated. That one page for Jam is nothing
compared to what is on the Ubuntu wiki, so I'll likely just reuse that
Great. Once things are set up, the team could consider using
for user-end documentation too:
Thanks for all your help. Still trying to get things organized, so
this is super helpful.
No worries. Thanks very much for taking an interest in the Jam SIG. :)
Ankur Sinha "FranciscoD" (He / Him / His) |
Time zone: Europe/London