Introductory mail
by Vipul Siddharth
Hello everyone,
This is Vipul Siddharth from Bengaluru India. I am a Red Hat intern and
have been contributing in fedora QA since may, 2016. Sumantro Mukherjee
introduced me to Fedora QA. I am looking forward to contribute in Fedora
commOps.
P.S. We recently had an activity where we introduced my college students to
Fedora.
Very soon i will come up with the blog :)
Thanks and regards
Vipul Siddharth
7 years, 7 months
Self introduction: Alexandre Moine & metrics idea
by Alexandre Moine
Hi,
My name is Alexandre Moine and I am a french student in computer science. I am working on fedora as a packager and an ambassador for now 4 years.
I am currently working for an event [1], and I found very difficult to find any stats about fedora. On the CommOps wiki page, there is some link about tools (fedora-stats-tool, gscoc-stats), but they are not very easy to use for the first, and too focused for the second.
I was thinking about a site that will provide all fedora basic-data (based on the great fedora apps datagrepper), like number of package added, number of user, with charts. We can also imagine a tool that will provide more specific datas/charts (number of wiki edit per day or number of crated iso by pungi per weeks) on demand.
This wiki page [2] have good ideas, but it is kind of outdated.
This can help ambassadors, like me now, or even all the part of the project: to now for example if a service is well used or not, or to see if a part of the project needs help.
There is here, I think, no huge difficulties. Datagrepper is really easy to use. It only require "some" website devel and intergration. I'm a not a professional dev, and I apologize in advance if my words are not wisely ;)
I am talking about a website because they are more friendly, but a great python tool will be very nice :)
Please tell me what you think about it, and if you have any ideas.
Alexandre
[1]: https://fedoraproject.org/wiki/Rencontres_Fedora_24_%C3%A0_Universciences
[2]: https://fedoraproject.org/wiki/Statistics_2.0
7 years, 7 months
Article about the workaround to solve login issues in the wiki due to the spam.
by Gabriele Trombini
Hi,
since Kevin found a workaround for the issue in the subject [1], I think it
is worth getting people aware of it in order to avoid further requests for
solution to each group.
More than an article, this could be considered a service notice, so there
ìs no need to write a big post.
I also think this is a kind of communication to be spread by the Magazine.
I'm not able to write anything because I'm moving for holidays and for some
days I'll have nothing to do with the PC.
Discussion is moving forward but this is the best workaround at the moment.
If someone will take care of writing please do.
Thanks
--
Gabri
[1]
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedora...
7 years, 7 months
Re: [Fedora-join] Discussion - issues with Fedora Join - solutions/ideas and TODOs?
by Sachin S. Kamath
On Mon, Aug 29, 2016 at 12:16 PM, Ankur Sinha <sanjay.ankur(a)gmail.com>
wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> Hiya,
>
Hi Ankur!
>
> Before I begin, if you're a member of the Fedora community already,
> please apply for membership to the fedora-join group in FAS[1].
> (That'll give us an idea of how many community members are interested
> in the SIG.) If you are a newbie and haven't introduced yourself yet,
> please do so.
>
> It's a somewhat long e-mail, but please bear with me and skim through
> it. I encourage *everyone* to reply to this e-mail with ideas/comments!
>
> Background and aim of this group
> - ---------------------------------
>
> For years now, we've heard that new potential contributors (henceforth
> referred to as "newbies") have a hard time joining the community. The
> reasons for this include, but are not limited to:
>
> - - newbies are timid (think squirrels!)
> - - newbies aren't used to the open source way of self education (Google
> the hell out of things, RTFM attitude, shamelessly ask questions if
> needed, NO spoon feeding and so on)
> - - newbies lose interest if they don't make friends and integrate into
> the community in a few weeks (few days?).
> - - the community is *vast*, spread over different teams with their own
> systems and procedures, and for someone new, finding the right
> people/channels/procedures can be quite daunting.
> - - community members are usually quite busy to give detailed replies -
> we're all volunteers here.
> - - more?
> So the idea of setting up the SIG was to set up channels of
> communication where newbies can come and in an extremely friendly
> environment form relationships within themselves, and with the
> community.
>
As tobi mentioned, mentorship sounds like a really good idea. This will
definitely help out a lot of so so-called "newbies" get started. I know how
it feels like to be one and I must say I was really hesitant to start
mailing list threads in the beginning. Apart from this, it'll also be a
nice idea to have weekly/bi-weekly/monthly meetings on the channel or any
of the fedora meeting channels to keep track of things and help newcomers
there. I see traces of fedora-join meetings in meetbot[1] but looks like
it's not active now. It'll be really nice if someone can step-up and
conduct meetings.
>
> For this to work, we need:
>
> - - the infrastructure. We have:
> * #fedora-join
> * this mailing list
> - - community members hanging out in these channels and willing to speak
> to newbies, help them get in touch with the right people, help them
> find the right resources, and so on.
> - - newbies.
>
> I hope this makes sense to everyone? Does everyone agree that the idea
> is a sane one? Any tweaks?
>
> How are we doing?
> - ------------------
>
> Well, not too good, I'd say. We've helped out some folks in the past,
> but we're not as active as we should be. Ideally, we should be up to
> our ears in e-mails and questions and people. So why aren't we?
>
> - - Part of this is of course because we're busy with other things;
> - - Part of this is also because we haven't managed to gain enough
> traction to get more members of the community involved in helping out
> at the group.
> - - I'm not sure the entire community is aware of the existence of the
> channels we've set up
> - - I'm not sure if we are visible enough for newbies to find us (for
> example, we're not on whatcanidoforfedora.org)
>
> Hmm, isn't the website a part of the Fedora Join effort to bring in more
contributors? I don't see how it'll fit in there. We can definitely have a
footer which says "More Questions? Talk to us on #fedora-join on Freenode"
or something along those lines.
> Other related reasons:
> - - we don't meet often (but do we need regular IRC meetings?)
>
> What can we do?
> - ---------------
>
> Now, this is the interesting bit! What do we do to improve the current
> state? Events (physical/IRC), make more noise, turn up in the right
> places, make ourselves more visible?
>
> Off the top of my head:
> - - We should make more noise to inform the community that we're here to
> help newbies get started
> - - I think we need to be better organised. For example, we don't have a
> SOP document (standard operating procedure) to guide either newbies or
> contributors to this group. Maybe we can set up a pagure repo where we
> open a new ticket for each newbie, and then close it when the newbie's
> integrated nicely with the community?
> - - We need to embrace metrics too - how many newbies do we have on this
> list? How many have we helped? Maybe we can set up a feedback form and
> request newbies to fill it out when they're ready? How many
> contributors do we have on this list? How often do people refer newbies
> to our channels?
>
I can work on the metrics part of it. I am working on a tool[2] to gather
user statistics and recently added a feature to get statistics of an entire
FAS group. The tool requires polishing and I'm planning to have a web
interface for it soon. If you guys can tell me what kind of stats/metrics
is required, I can ready 'em up :)
- - We need to integrate better with the community - we seem to be a
> standalone group at the moment, and that just won't work. Maybe we
> could integrate with CommOps better, since CommOps has members from the
> different teams?
>
Sounds like a plan, I will open a ticket regarding this and discuss in
tomorrow's CommOps meeting.
cc-ing CommOps here for more comments.
> - - Maybe an IRC meeting a month just to keep ourselves active wouldn't
> be such a bad idea?
>
+1
> - - The fas group is only for community members, do we need another for
> newbies? Should we just open the group to newbies? (This can then be
> used to give them wiki access which has been limited to cla+1 to deal
> with spam.)
>
Spammers are social engineering a lot nowadays. We cannot really afford to
open up to new contributors just yet.
> - - What else?
>
>
> Please, add to this list!
>
>
> Other stuff
> - ------------
>
> Please do keep up with the Fedora hubs initiative[2]. It's going to be
> marvellous! It also has some functionality to enable people to join
> groups, but I still don't think it's a complete replacement for good
> old school conversation when it comes to forming relationships.
>
>
> Please, do reply to this e-mail with whatever ideas you have - we can't
> improve things without ideas and discussion.
>
> I'm still drowning in work, but when I do have time off (like this long
> weekend!), I'm going to be active. Most of you know that I lurk in a
> lot of fedora channels as FranciscoD, please feel free to ping me.
>
> [1] https://admin.fedoraproject.org/accounts/group/view/fedora-join
> [2] https://fedoramagazine.org/5tftw-2015-06-19/
> - --
> Thanks,
> Regards,
> Ankur Sinha "FranciscoD"
>
> http://fedoraproject.org/wiki/User:Ankursinha
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2
>
> iQEcBAEBCAAGBQJXxF/7AAoJEPjYwL66yJi90g8IAJKimXJRaGhbEIpKnYrpTRyk
> ltCHacYwwSpI2LJBKtmdvtZ9WU87r9/UgHDxOs8AB/BkFML56h6TU+jAkOOmo0CA
> i9anYGk9gcinBrWhEx43uKBlEEDKzX0abCKn0YlbWZbCVYml+Es5GnRMZjYNoTK+
> tvUz6S3giWJPM+RD13dDQKXtEBW+Ep2dZkuDD/V4EWM6xFeJLeKbPyEs3U8Owr4Y
> RyNTE0IEUoldohQKbeTyEfIbgXbuBOUl3QV31kZUiVZKHo3LFYO11dw2XZCVzUgC
> O/Rc2B2CQCJh1soT/p6Y+sarpBWd65v/P96EFNUsiiQodMXCv8/4ja8WP9gjSi4=
> =92aM
> -----END PGP SIGNATURE-----
> _______________________________________________
> fedora-join mailing list
> fedora-join(a)lists.fedoraproject.org
> https://lists.fedoraproject.org/admin/lists/fedora-join@
> lists.fedoraproject.org
>
--
Cheers,
Sachin S. Kamath
https://www.sachinwrites.xyz
[1]
https://meetbot.fedoraproject.org/sresults/?group_id=fedora-join&type=team
[2] https://pagure.io/gsoc-stats
7 years, 8 months
[Minutes] [2016-08-30] Python SIG, TRAC IS NO MORE, new meeting time?, wiki gardening
by Justin W. Flory
Hey all! Today was a packed meeting - apologies for running late today
and being so disorganized. It's only Tuesday but this week has been crazy...
In today's meeting, we spent a lot of time focusing on the Python SIG
on-boarding steps and identifying action items and our own steps for
tackling this ticket. Also, we moved from Trac to Pagure last night
(more on this in another email)! There's also some pending wiki
gardening to do from this move.
We also very, very briefly discussed a new meeting time since the
current start time no longer works for me by 30 minutes. I'm going to
formally propose pushing the meeting time in a ticket and we can take a
vote.
= = = = =
Meeting ended Tue Aug 30 17:31:37 2016 UTC.
Minutes:
https://meetbot.fedoraproject.org/fedora-meeting/2016-08-30/commops.2016-...
Minutes (text):
https://meetbot.fedoraproject.org/fedora-meeting/2016-08-30/commops.2016-...
Log:
https://meetbot.fedoraproject.org/fedora-meeting/2016-08-30/commops.2016-...
* * * * *
============================================
#fedora-meeting: Fedora CommOps (2016-08-30)
============================================
Meeting started by skamath at 15:58:17 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/fedora-meeting/2016-08-30/commops.2016-...
.
Meeting summary
---------------
* Agenda (skamath, 15:58:41)
* LINK: https://fedoraproject.org/wiki/Meeting:CommOps_2016-08-30
(skamath, 15:58:53)
* (1) Roll Call / Q&A (skamath, 15:58:58)
* (2) Announcements (skamath, 15:59:14)
* (3) Action items from last meeting (skamath, 15:59:19)
* (4) Tickets (skamath, 15:59:23)
* (5) Wiki Gardening (skamath, 15:59:27)
* (6) Community Blog (skamath, 15:59:31)
* (7) Release Schedule (skamath, 15:59:37)
* (8) Open Floor (skamath, 15:59:41)
* Roll Call / Q&A (skamath, 15:59:47)
* Michael Downey; UTC -7:00; CommOps, Marketing, also <3 for gsoc,
docs, design, * (downey, 15:59:56)
* Name; Timezone; Sub-projects/Interest Areas (skamath, 15:59:56)
* Sachin S. Kamath; UTC +5.30; CommOps, Metrics, GSoC, * (skamath,
16:00:31)
* Announcements (skamath, 16:03:36)
* === Fedora 25 Alpha releases today === (skamath, 16:03:43)
* LINK:
https://lists.fedoraproject.org/archives/list/marketing@lists.fedoraproje...
(skamath, 16:03:50)
* LINK: https://fedoraproject.org/wiki/F25_Alpha_release_announcement
(skamath, 16:03:56)
* Fedora 25 Alpha releases today. The alpha release announcement is in
final drafting. (skamath, 16:04:02)
* === "The final results of Google Summer of Code '16 has been
announced" === (skamath, 16:04:13)
* LINK: http://summerofcode.withgoogle.com/how-it-works/ (skamath,
16:04:21)
* The final results of GSoC was announced today. This marks the end of
this years' GSoC (skamath, 16:04:53)
* Dhanesh B. Sabane, UTC+5:30, CommOps, ML, Packaging, Linux Kernel
(dhanesh95_, 16:05:20)
* Action items from last meeting (skamath, 16:07:05)
* LINK:
https://meetbot.fedoraproject.org/fedora-meeting/2016-08-23/commops.2016-...
(skamath, 16:07:11)
* How This Works: We look at past #action items from the last meeting
for quick follow-up. If a task is completed, we move on to the next
one. If it isn't, we get an update and re-action it if needed. If no
status, we'll try to get a quick update and move forward. (skamath,
16:07:17)
* === downey Ping jflory7 for editing article / adding paragraph into
article === (skamath, 16:07:23)
* downey a new article pending review on magazine, and contains the
edits for the old article and is all set to go (skamath, 16:08:12)
* === jflory7 Work with bee2502 on writing a report / update on the
Flock 2016 CommOps workshop === (skamath, 16:08:24)
* ACTION: jflory7 Work with bee2502 on writing a report / update on
the Flock 2016 CommOps workshop (skamath, 16:09:24)
* === jflory7 bee2502 Take workshop feedback and parse it into more
accessible data (e.g. tickets / commits / CommBlog posts / metrics /
etc.) === (skamath, 16:09:31)
* ACTION: jflory7 bee2502 Take workshop feedback and parse it into
more accessible data (e.g. tickets / commits / CommBlog posts /
metrics / etc.) (skamath, 16:09:44)
* === jflory7 Review emails for pending posts on the CommBlog ===
(skamath, 16:09:54)
* Wesley Otugo; UTC +1 (wesleydekstar_, 16:10:06)
* ACTION: jflory7 Review emails for pending posts on the CommBlog
(skamath, 16:11:11)
* === jflory7 Update Community Blog writing guide for writing a new
article based on what's actually happening in 2016 now ===
(skamath, 16:11:22)
* ACTION: jflory7 Update Community Blog writing guide for writing a
new article based on what's actually happening in 2016 now
(skamath, 16:11:37)
* ACTION: jflory7 Sort through ideas on reviewing old contributor
discussion, form proposals in the ticket, share at next meeting
(skamath, 16:12:38)
* LINK: https://pagure.io/fedora-commops/ (skamath, 16:13:09)
* === [INCOMPLETE] skamath File a ticket in Fedora Infra Trac for
proposing an official migration from fedora-infra GitHub
organization into Pagure === (skamath, 16:13:20)
* ACTION: skamath File a ticket in Fedora Infra Trac for proposing an
official migration from fedora-infra GitHub organization into Pagure
(skamath, 16:13:29)
* === jflory7 Reach out to decause about the idea of migrating his
tools in the CommOps toolbox to Pagure and granting access to the
CommOps group === (skamath, 16:14:02)
* ACTION: skamath Reach out to decause about the idea of migrating his
tools in the CommOps toolbox to Pagure and granting access to the
CommOps group (skamath, 16:14:26)
* ACTION: jflory7 Follow up on Pagure importer tool for use with
decause's CommOps toolbox repositories (jflory7, 16:22:18)
* === [COMPLETE] jflory7 Do a social media blast promoting the FOSS
Wave article for Bhopal === (jflory7, 16:23:28)
* === [COMPLETE] jflory7 Revisit wiki spam article with context of
current situation with FAS groups === (jflory7, 16:23:45)
* Article scheduled for Thursday; modified for accuracy with current
wikieditor situation (jflory7, 16:24:04)
* Tickets (jflory7, 16:26:23)
* LINK: https://pagure.io/fedora-commops/issues?tags=meeting
(jflory7, 16:26:53)
* === Ticket #81 === (jflory7, 16:27:26)
* "Migrating to Pagure" (jflory7, 16:27:30)
* LINK: https://pagure.io/fedora-commops/issue/81 (jflory7,
16:27:34)
* Successfully migrated to Pagure last night as scheduled; Trac will
no longer be an active part of our workflow. Trac will be kept up
for another month before a Fedora Infra ticket will be filed
requesting it to be dropped off. (jflory7, 16:28:47)
* ACTION: jflory7 Remove Ticket #81 from meeting agenda (jflory7,
16:28:59)
* === Ticket #82 === (jflory7, 16:30:21)
* "Move CommOps toolbox to Pagure" (jflory7, 16:30:26)
* LINK: https://pagure.io/fedora-commops/issue/82 (jflory7,
16:30:31)
* LINK: https://pagure.io/pagure-importer (jflory7, 16:31:01)
* LINK: https://fedoraproject.org/wiki/CommOps#Toolbox (jflory7,
16:31:11)
* AGREED: Will work on migrating GitHub repos to Pagure to increase
accessibility and visibility of useful metrics or data visualization
tools for other community members (jflory7, 16:35:04)
* === Ticket #84 === (jflory7, 16:35:26)
* "Python SIG Onboarding" (jflory7, 16:35:32)
* LINK: https://pagure.io/fedora-commops/issue/84 (jflory7,
16:35:37)
* LINK: https://badges.fedoraproject.org/badge/python-sig-member
(skamath, 16:37:22)
* LINK: https://badges.fedoraproject.org/tags/python/any (skamath,
16:41:58)
* IDEA: Using the Parselmouth badge series as beginning steps for
participation in Python SIG (porting packages from Python 2 to 3)
(jflory7, 16:42:58)
* IDEA: Changing the name of the FAS group or more clearly
communicating the security clearance required for sponsorship into
the FAS group (jflory7, 16:43:23)
* IDEA: Wiki gardening to organize info about the SIG and how to
participate (jflory7, 16:44:01)
* ACTION: jflory7 Start IRC / mailing list discussion on wiki
gardening for Python SIG (jflory7, 16:56:44)
* LINK: https://fedoraproject.org/wiki/User:Dhanesh95/SIGs/Python
(jflory7, 16:58:04)
* ACTION: jflory7 Do some srs ticket triaging / updating this week
(jflory7, 17:02:17)
* Newcomer introduction (jflory7, 17:02:29)
* ACTION: amitsin6h Double-check subscription to the mailing list and
make sure you are receiving mail from the list (jflory7, 17:10:19)
* Wiki Gardening (jflory7, 17:10:41)
* ACTION: jflory7 Come up with a more fitting introductory item to
place into the meeting (jflory7, 17:11:26)
* HELP: CommOps wiki page needs to remove all mention of Trac and
replace with Pagure (jflory7, 17:11:37)
* ACTION: jflory7 Revisit Join page and edit / alter section about
wiki page (jflory7, 17:11:50)
* ACTION: skamath Garden the CommOps wiki page to remove mention of
Trac and replace with Pagure (and update hyperlinks) (jflory7,
17:12:42)
* ACTION: downey Migrate the member table from
https://fedoraproject.org/wiki/CommOps#Interest_Areas to
https://fedoraproject.org/wiki/CommOps/Members (jflory7, 17:15:55)
* Community Blog (jflory7, 17:16:59)
* How this is supposed to work: There is a quick blast of information
about what was published in the past week with some metrics,
followed by posts that are being drafted. After the information
blast, the floor is opened for any Community Blog-related
discussion. (jflory7, 17:17:15)
* How it's happening today: jflory7 didn't have time to prep any of
the data or go through numbers, so he is going to compensate at next
week's meeting (jflory7, 17:17:46)
* Release Schedule (jflory7, 17:19:41)
* LINK:
https://fedorapeople.org/groups/schedule/f-25/f-25-key-tasks.html
(jflory7, 17:19:57)
* (1) Alpha Release Public Availability (Tue 2016-08-30) (jflory7,
17:20:16)
* (2) Software Translation Deadline (due: Tue 2016-09-13) (jflory7,
17:20:31)
* (3) Change Checkpoint: 100% Code Complete Deadline (Tue 2016-09-27)
(jflory7, 17:21:06)
* (4) Beta Freeze (00:00 UTC) (Tue 2016-09-27) (jflory7, 17:21:20)
* Open Floor (jflory7, 17:22:25)
* LINK: https://fedoraproject.org/wiki/G11N/vFAD_Translation_F25
(pravins, 17:22:28)
* LINK:
https://badges.fedoraproject.org/badge/fedora-25-translation-sprint
(jflory7, 17:22:53)
* LINK:
https://lists.fedoraproject.org/archives/list/commops@lists.fedoraproject...
(skamath, 17:23:19)
* jflory7 apologizes for being super late without any warning *and*
dropping the ball on the agenda today - skamath is super awesome for
picking up the slack and carrying the torch! (jflory7, 17:28:15)
* Asked about bumping the meeting time ahead by 30 minutes for
jflory7's new schedule - will ask on the mailing list and/or a
ticket to finalize opinions ASAP (jflory7, 17:30:06)
Meeting ended at 17:31:37 UTC.
Action Items
------------
* jflory7 Work with bee2502 on writing a report / update on the Flock
2016 CommOps workshop
* jflory7 bee2502 Take workshop feedback and parse it into more
accessible data (e.g. tickets / commits / CommBlog posts / metrics /
etc.)
* jflory7 Review emails for pending posts on the CommBlog
* jflory7 Update Community Blog writing guide for writing a new article
based on what's actually happening in 2016 now
* jflory7 Sort through ideas on reviewing old contributor discussion,
form proposals in the ticket, share at next meeting
* skamath File a ticket in Fedora Infra Trac for proposing an official
migration from fedora-infra GitHub organization into Pagure
* skamath Reach out to decause about the idea of migrating his tools in
the CommOps toolbox to Pagure and granting access to the CommOps group
* jflory7 Follow up on Pagure importer tool for use with decause's
CommOps toolbox repositories
* jflory7 Remove Ticket #81 from meeting agenda
* jflory7 Start IRC / mailing list discussion on wiki gardening for
Python SIG
* jflory7 Do some srs ticket triaging / updating this week
* amitsin6h Double-check subscription to the mailing list and make sure
you are receiving mail from the list
* jflory7 Come up with a more fitting introductory item to place into
the meeting
* jflory7 Revisit Join page and edit / alter section about wiki page
* skamath Garden the CommOps wiki page to remove mention of Trac and
replace with Pagure (and update hyperlinks)
* downey Migrate the member table from
https://fedoraproject.org/wiki/CommOps#Interest_Areas to
https://fedoraproject.org/wiki/CommOps/Members
Action Items, by person
-----------------------
* amitsin6h
* amitsin6h Double-check subscription to the mailing list and make
sure you are receiving mail from the list
* decause
* skamath Reach out to decause about the idea of migrating his tools
in the CommOps toolbox to Pagure and granting access to the CommOps
group
* jflory7 Follow up on Pagure importer tool for use with decause's
CommOps toolbox repositories
* downey
* downey Migrate the member table from
https://fedoraproject.org/wiki/CommOps#Interest_Areas to
https://fedoraproject.org/wiki/CommOps/Members
* jflory7
* jflory7 Work with bee2502 on writing a report / update on the Flock
2016 CommOps workshop
* jflory7 bee2502 Take workshop feedback and parse it into more
accessible data (e.g. tickets / commits / CommBlog posts / metrics /
etc.)
* jflory7 Review emails for pending posts on the CommBlog
* jflory7 Update Community Blog writing guide for writing a new
article based on what's actually happening in 2016 now
* jflory7 Sort through ideas on reviewing old contributor discussion,
form proposals in the ticket, share at next meeting
* jflory7 Follow up on Pagure importer tool for use with decause's
CommOps toolbox repositories
* jflory7 Remove Ticket #81 from meeting agenda
* jflory7 Start IRC / mailing list discussion on wiki gardening for
Python SIG
* jflory7 Do some srs ticket triaging / updating this week
* jflory7 Come up with a more fitting introductory item to place into
the meeting
* jflory7 Revisit Join page and edit / alter section about wiki page
* skamath
* skamath File a ticket in Fedora Infra Trac for proposing an official
migration from fedora-infra GitHub organization into Pagure
* skamath Reach out to decause about the idea of migrating his tools
in the CommOps toolbox to Pagure and granting access to the CommOps
group
* skamath Garden the CommOps wiki page to remove mention of Trac and
replace with Pagure (and update hyperlinks)
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* jflory7 (234)
* skamath (175)
* dhanesh95 (34)
* downey (27)
* zodbot (19)
* amitsin6h (19)
* decause (13)
* devyani7 (10)
* FranciscoD (9)
* pravins (6)
* dhanesh95_ (3)
* bt0 (2)
* wesleydekstar_ (1)
* decause_ (1)
* commops (0)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
--
Cheers,
Justin W. Flory
jflory7(a)gmail.com
7 years, 8 months
Introduction Email: Muhammad Ahsan
by Muhammad Ahsan
Hello,
My name is Ahsan and I have just joined the list as a contributor. I am totally new to Fedora contributors community but ancient while working on Fedora. I have used all the Fedora distributions till Fedora 23 (my current default distribution) and safely say that I am an intermediate to advance level user. I am looking for some mentor to contribute to Fedora. I am an avid user and advocate of open source softwares. Having used many really good open source softwares, I feel that I should return something back to the OS community and this is a small attempt to do so.
Regards,
Ahsan
7 years, 8 months
Wiki Spam Post - Pending Review
by Brian Exelbierd
I am resending this in a separate thread to get it some visibility.
regards,
bex
----- Original message -----
From: Brian Exelbierd <bex(a)pobox.com>
To: commops(a)lists.fedoraproject.org
Subject: [commops] Re: Article about the workaround to solve login issues in the wiki due to the spam.
Date: Tue, 16 Aug 2016 11:45:13 +0200
On Mon, Aug 15, 2016, at 07:17 PM, Gabriele Trombini wrote:
>
> Hi,
>
> since Kevin found a workaround for the issue in the subject [1], I
> think it is worth getting people aware of it in order to avoid further
> requests for solution to each group.
> More than an article, this could be considered a service notice, so
> there ìs no need to write a big post.
> I also think this is a kind of communication to be spread by the
> Magazine.
>
> I'm not able to write anything because I'm moving for holidays and for
> some days I'll have nothing to do with the PC.
>
> Discussion is moving forward but this is the best workaround at
> the moment.
>
> If someone will take care of writing please do.
I believe it is worthwhile to put something on the Comm Blog. I do not
think this should be in the Magazine.
I drafted a short item here:
https://communityblog.fedoraproject.org/?p=2208&preview_id=2208&preview=true
https://communityblog.fedoraproject.org/wp-admin/post.php?post=2208&actio...
Your feedback is appreciated.
regards,
bex
_________________________________________________
Fedora Community Operations (CommOps) mailing list
commops(a)lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/commops@lists.fedoraproject.org
7 years, 8 months
