Easyfix + WhatCanIDoForFedora
by Brian Exelbierd
I started writing this a while ago and never got it fully formed. Rather than let it keep rotting in my drafts folder I wanted to share it and see if it made sense to anyone else.
Warning - rough edges ahead!
---
Conversations with several people have resulted in distilling the following idea:
= EasyFix
== Changing metadata
Modify the table that drives fedoraproject.org/easyfix that is located at https://fedoraproject.org/wiki/Easyfix
The table would now include two additional columns (optional)
Col 1 = existing reference to the issue tracker. We should consider adding gitlab.com support
Col 2 = existing point of contact
Col 3 = category of task (documentation, infrastructure, programming-Haskell, programming-Ruby, etc.)
Col 4 = SIG/WG/etc. this project is related too (Design, Council, KDE, etc.)
== Changing fedoraproject.org/easyfix
Today we show only two categories: Issues from Pagure/Github and Bugzillas
I believe those categories are not the right categories for consumers of the page. Using the new category (col 3) above, we would break things out by the kind of contribution. This would serve to let people browse related tasks more easily and to reduce the overwhelming nature of the current lists.
For BZs we are either going to have to guess based on BZ metadata or leave them lumped together.
= WCIDFF
WCDIFF should be extended to show the categories and groups appropriate for the various endpoints. This way the person who navigates WCDIFF has the option of reading a specific task they could work on right now, if they so desire.
= Marketing/Promotion
The categories give us the opportunity to promote our easyfixes as a great way to join or contribute in a targeted manner. This could come in the form of articles, tweets, or live conference appearances.
What do people think?
regards,
bex
4 years, 12 months
Communityblog Pending Posts
by Perry Rivera
Hello all:
Might anyone know the status of the two pending posts for Author: lajuggler?
Pending Posts:
1) Fedora at SCaLE 16x (2018) Event Report – Pasadena, California
2) Fedora at OSSNA 2017 Event Report – Los Angeles, California
Thank you,
Perry Rivera
lajuggler
5 years, 4 months
Re: [Release] pagure 4.0 and 4.0.1
by Justin W. Flory
Hi, congrats Pagure team for a new major release!! This is awesome news!
Has anyone considered writing a summary Community Blog article about the
new major release?
I believe there is significant interest in something like an article to
summarize the release. I want to know more about how the project was
changed for better extensibility, a little bit on the CI changes,
marking milestones as active / inactive, linking issues from pull
requests (<3), and deleting a branch after a PR is merged.
Updates from GitHub and GitLab on their blogs helps keep me informed
about their projects and what is changing. It would be great to have an
article to share and talk about Pagure, link on social media, etc. It
would help keep me better informed about the project and new major
releases like this one.
This Pagure release had a lot of things I have really wanted. I am sure
there are others who are excited by this changelog but don't know they
are excited yet. I think a Community Blog article would help capture the
awesome work that went into this release and better inform users of
Pagure who are not members of Fedora Infrastructure (Ambassadors,
Marketing, CommOps, Translations, Docs, etc.).
A Community Blog article to summarize this major release would be
awesome. I am happy to help support this, but I don't have enough
information to write the article myself. Let me know if I can do
anything to help.
---
Also, this fix is especially awesome!! This one has been bugging for me
so long but I would always forget to file it as a bug because I didn't
know it was because of colors:
- Fix allowing to add multiple tags with the same color
On 04/26/2018 10:05 AM, Pierre-Yves Chibon wrote:
> Good Morning Everyone,
>
> Earlier today we released a new major version of pagure: 4.0.
> Following it, we were informed about two small bugs, one of which did not impact
> any of our running pagure instances, the other would have been annoying in
> dist-git.
> So we fixed them and released 4.0.1.
>
> Here are the two changelogs (flood incoming!):
>
> 4.0.1 (2018-04-26)
> ------------------
>
> - Fix browsing projects in a namespace when logged in and the instance has only
> one contributor for every projects
> - Fix commenting on a PR or an issue if the event source server is not
> configured at all (Slavek Kabrda)
>
>
> 4.0 (2018-04-26)
> ----------------
>
> - Re-architecture the project to allow potentially extending pagure outside of
> its core
> - Fix running the tests on newer pygit
> - Add a space between the fork and the watch buttons
> - Add a global configuration option to turn on or off fedmsg notifications for
> the entire pagure instance
> - Set the default username to be 'Pagure' when sending git commit notifications
> by email
> - Add project setting to show roadmap by default (Vivek Anand)
> - Explain in the doc where the doc is coming from
> - Expand and document the tokenization search
> - Add document that multiple keys are supported
> - Add a way to block non fast-forwardable commits on all branches
> - Fix running pagure on docker for development (Clément Verna)
> - Make the accordeon in the settings page work correctly
> - Allow calling git blame on a commit instead of a branch
> - Exclude the .pyc files from all folders
> - Fix viewing file if the identifier provider is a commit hash
> - Make pagure-ci use python-jenkins to work with newer Jenkins
> - Fix the link to the pull-request shown by the default git hook
> - If the tag's color is the default text, convert it to the hex value
> - Include documentation on how to pull locally a pull-request on the PR page
> - Properly retrieve the number of projects and forks users have
> - Replace jquery.dotdotdot by jquery.expander
> - Update the Preview button to display 'Edit' when previewing
> - Fix supporting <link> in markdown as it is supposed to be
> - Add missing authentication provider option to documentation (Michael Watters)
> - Fix couple of places where fullname is required while it's not
> - Let users see and access private tickets they are assigned to
> - Fix allowing to add multiple tags with the same color
> - Add a new API endpoint allowing to open new pull-requests
> - Fix checking if the user is authenticated
> - Add the possibility to mark milestones as active or inactive
> - Fix making the milestones showing in the correct order on the issue page
> - Fix showing the proper URLs in the repo overview
> - Include the cached merge status in the JSON representation of pull-requests
> - Improve the fedmsg git hook documentation
> - Fix display of deleted parent on index page (Lubomír Sedlář)
> - Adjust message shown to the user deleting a tag off a project
> - Fix redirecting the user when they remove themselves from a project
> - Add an option to notify on flags being added to a pull-request
> - Add an option to notify on flags being added to a commit
> - Document project intra-pagure hyperlinks
> - Refresh the PR cache of the parent repo rather than always the current one
> - Move the webhook service to be a celery service
> - Fix dead-link due to documentation for python-markdown being moved
> - Mention #pagure IRC channel in Contributing docs (Peter Oliver)
> - Fix editing and deleting comments added by the EV server to PRs
> - Include a count of the number of tickets shown vs recorded for each milestone
> - Do not try to get the avatar if the author has no email
> - Fix HTML on settings page
> - Migrate the logcom service to be celery based and triggered
> - Link directly to API key settings in error message about expired API key
> (Peter Oliver)
> - Drop the constraint on binaryornot
> - Make fork page header link consistent (Lubomír Sedlář)
> - Fix the rtd hook and port it to the v2 API (Clément Verna, Pierre-Yves Chibon)
> - Deduplicate list of contributors to a project (Lubomír Sedlář)
> - Remove repo from gitolite cache when it gets deleted (Slavek Kabrda)
> - Make the hooks use the new architecture (Clément Verna)
> - Switch to comments on PR page when url fragment is reset (Lubomír Sedlář)
> - Handle implicit issue link at start of line (Adam Williamson)
> - Don't treat @ in the middle of words as a mention (Adam Williamson)
> - Improve the CI settings docs (Clément Verna)
> - Ensure the tasks has finished before checking its results
> - Fix oidc logout with admin_session_timedout (Slavek Kabrda)
> - Make images be lazy loaded via javascript
> - Adjust activity heatmap and logs for timezone (Adam Williamson)
> - Use timezone not offset for user activity, fix heat map (Adam Williamson)
> - JS clean up (Lubomír Sedlář)
> - Fix UnicodeEncode on entering non-ascii password (Farhaan Bukhsh)
> - Add Tests and exception for non-unicode password (Farhaan Bukhsh)
> - Forbid adding tags with a slash in their name to a project
> - Migrate the loadjson service to be celery-based
> - Specify which service is logging the action for easier debugging/reading of
> the logs
> - Merge the fedmsg notifications on commit logic into the default hook
> - Merge pagure-ci into the pagure's celery-based services
> - When creating a new PR, allow updating the branch from
> - Allow pull changes from a different repo than the parent one
> - Add a new internal endpoint to get the family of a project
> - Expand the API endpoint listing tags to include the hash if asked t
> - List the tags of the project in the list of commits
> - Fix sending notifications in the default hook
> - Make it possible to use custom PR/commit flags based on instance configuration
> (Slavek Kabrda)
> - Show summary of flags on page with commits list (Slavek Kabrda)
> - Improve the info message when trying to setup an user with a known email
> - Make badges with flag counts in commits list to links to commit details
> (Slavek Kabrda)
> - Enable sending messages to stomp-compliant brokers (Slavek Kabrda)
> - Update required pygit2 version (Clément Verna)
> - Do not crash when getting the branches ready for PR on a fork with no parent
> - Adjust tests for newer flask
> - Make trigger CI build depends on project name (Clément Verna)
> - Ensure the DOCS_FOLDER and TICKETS_FOLDER really are optional
> - Move the `Add Milestone` button near the top and fix the layout
> - Add a button to delete empty line when adding new tags
> - Change submit button labels for issues and PRs (Akshay Gaikwad)
> - Add changelog.rst (Akshay Gaikwad)
> - Overflow heatmap automatically (Paul W. Frields)
> - Large unit-tests improvement both in quality and speed (Aurélien Bompard)
> - Initial support for commit CI trigger (Clément Verna)
> - Added signed-off-by during web ui commit (yadneshk)
> - Replace py-bcrypt by python2-bcrypt (Clément Verna)
> - Fix the user's requests page
> - Establish an order for readme files (Karsten Hopp)
> - Include the filename when showing the diff of remote PRs
> - Specify the parent repo, even when creating a remote PR
> - Always use md5 to get ssh key information (Patrick Uiterwijk)
> - Support showing comment submitted by ajax when the SSE is down/not set
> - Add the possibility to link issues to pull-requests (in the UI)
> - Rely on the list of branches rather than the ``.empty`` attribute to find out
> if a git repo is empty or not
> - Add the possibility to split the tasks into multiple queues
> - Fix getting the patch of a PR that no longer has a project from
> - Do not update the CHECKSUMS file if the file was already uploaded
> - Show the fork button on forks
> - Make the web-hook field be a textarea and improve the documentation about
> web-hook
> - Fix supporting branches containing multiple dots
> - Do not convert to markdown commit messages in notifications
> - Port pagure to use the compile-1 script from upstream gitolite (if
> configured to do so) (Slavek Kabrda)
> - Add preview when editing a comment (Rahul Bajaj) and the initial comment
> - Ensure that deployment keys are managed correctly (Michael Watters)
> - Improve human-readable date/time display in web UI (Adam Williamson)
> - Make sure we rollback session on task failures (Slavek Kabrda)
> - Fix new commit notification mails with non-ASCII (#1814) (Adam Williamson)
> - Don't create gitolite.conf entries for docs and tickets when they're disabled (Slavek Kabrda)
> - Move source git urls above contibutors list (yadneshk)
> - Fix private repo to be accessed by ACLs other than admin (Farhaan Bukhsh)
> - Change the lock name based on the git repo touched (Pierre-Yves Chibon)
> - Adjust the spec file, remove no longer needed lines and fix requirements (Pierre-Yves Chibon)
> - Add example worker systemd service file (Pierre-Yves Chibon)
> - Adjust the wsgi file for the new arch (Pierre-Yves Chibon)
> - Fix turning the read-only boolean on a fork (Pierre-Yves Chibon)
> - Support blaming a file is the identifier is a tag (Pierre-Yves Chibon)
> - Ensure the git hooks are always executable in the rpm (Pierre-Yves Chibon)
> - Do not syntax highlight 'huge' files (Patrick Uiterwijk)
> - Fix exceptions caused by missing merge object (Michael Watters)
> - Fix linking to a PR that was opened from a main project to a fork (Pierre-Yves
> Chibon)
> - Add support for repository templates for sources and forks (Pierre-Yves
> Chibon)
> - Enable usage of flask-session extension (Slavek Kabrda)
> - Add a configuration key allowing to send fedmsg notifications on all commits
> (Pierre-Yves Chibon)
> - Allow deleting branch when PR is merged (Lubomír Sedlář)
>
>
> If you made it until here, congratulations!
>
> Oh and 4.0.1 is currently happily running in stg.pagure.io and src.stg.fp.o :)
>
>
> Happy hacking,
> Pierre
>
>
>
> _______________________________________________
> infrastructure mailing list -- infrastructure(a)lists.fedoraproject.org
> To unsubscribe send an email to infrastructure-leave(a)lists.fedoraproject.org
>
--
Cheers,
Justin W. Flory
jflory7(a)gmail.com
5 years, 5 months
[Minutes] [2018-04-30] Contributor stories outreach, abstract on-boarding guidelines, podcast outline
by Justin W. Flory
Hi all! This week's CommOps meeting ended a few minutes ago.
Quick summary:
* Contributor stories intro outreach (social media / announce ML)
* Creating general on-boarding guidelines for Fedora teams
* Creating an outline for Fedora CommOps podcast interview w/ x3mboy
I will be unavailable for the next two weeks (maybe three) of meetings,
so bt0 is chairing for May 7 and May 14 meetings.
See you around in the Fedora-universe!
= = = = =
Meeting ended Mon Apr 30 15:32:22 2018 UTC.
Minutes:
https://meetbot.fedoraproject.org/fedora-commops/2018-04-30/commops.2018-...
Minutes (text):
https://meetbot.fedoraproject.org/fedora-commops/2018-04-30/commops.2018-...
Log:
https://meetbot.fedoraproject.org/fedora-commops/2018-04-30/commops.2018-...
* * * * *
============================================
#fedora-commops: Fedora CommOps (2018-04-30)
============================================
Meeting started by jwf at 14:30:32 UTC. The full logs are available at
https://meetbot.fedoraproject.org/fedora-commops/2018-04-30/commops.2018-...
.
Meeting summary
---------------
* Agenda (jwf, 14:30:37)
* LINK:
https://infinote.fedoraproject.org/cgit/infinote/tree/meeting-templates/f...
(jwf, 14:30:44)
* (1) Roll call / Q&A (jwf, 14:30:44)
* (2) Announcements (jwf, 14:30:44)
* (3) Action items from last meeting (jwf, 14:30:45)
* (4) Tickets (jwf, 14:30:48)
* (5) Open floor (jwf, 14:30:50)
* Roll call / Q&A (jwf, 14:30:55)
* Name; Timezone; Sub-projects/Interest Areas (jwf, 14:30:57)
* ACTION: commops New members, make sure you introduce yourself on the
CommOps mailing list [ https://fedoraproject.org/wiki/CommOps/Join ]
(jwf, 14:30:57)
* Justin W. Flory; UTC-5; CommOps, Diversity & Inclusion Team,
Ambassadors, Mindshare (jwf, 14:31:23)
* Alberto Rodriguez Sanchez;UTC-5; CommOps, Marketing, dotNet sig,
Ambassadors and more (bt0, 14:33:35)
* Announcements (jwf, 14:39:12)
* === "Commitment to community: Fedora CommOps FAD 2018" === (jwf,
14:39:26)
* LINK:
https://communityblog.fedoraproject.org/fedora-commops-fad-2018/
(jwf, 14:39:26)
* The 2018 CommOps FAD event report is now published. Understand your
Fedora sub-project with charts / graphs and see how to thank other
contributors for Fedora Appreciation Week. (jwf, 14:39:27)
* === "How to use Fedora Wiki as your wiki whiteboard" === (jwf,
14:39:39)
* LINK:
https://communityblog.fedoraproject.org/how-to-fedora-wiki-whiteboard/
(jwf, 14:39:40)
* Get a quick overview of using the Fedora Wiki and its syntax from
wesleyotugo. (jwf, 14:39:40)
* === "Top Badgers of 2017: Carl George" === (jwf, 14:39:46)
* LINK:
https://communityblog.fedoraproject.org/top-badgers-2017-carl-george/
(jwf, 14:39:47)
* Check out the last post in 'Top Badgers of 2017' series by lroca.
roca++ for creating and driving this interview series! (jwf,
14:39:47)
* === Fedora 28 releases tomorrow! === (jwf, 14:40:40)
* LINK:
https://communityblog.fedoraproject.org/fedora-28-release-dates-schedule/
(jwf, 14:40:55)
* Fedora 28 comes out tomorrow! Get ready to try out the latest and
greatest that the Fedora community has put together over the last
six months. (jwf, 14:41:16)
* Action items from last meeting (jwf, 14:42:05)
* LINK:
https://meetbot.fedoraproject.org/fedora-commops/2018-04-23/commops.2018-...
(jwf, 14:42: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 if needed. If no
status, we'll try to get a quick update and move forward. (jwf,
14:42:11)
* === [COMPLETE] "@x3mboy File a new ticket in Mindshare Pagure to
propose student pack idea and start discussion in Mindshare
Committee" === (jwf, 14:42:30)
* LINK: https://pagure.io/mindshare/issue/16 (jwf, 14:42:31)
* x3mboy started this discussion in the Mindshare Committee Pagure.
Subscribe to the issue there to keep up with the student pack
planning. (jwf, 14:42:31)
* === [COMPLETE] "x3mboy Submit new PR with README for
contributor-stories repository" === (jwf, 14:42:43)
* LINK:
https://pagure.io/fedora-commops/contributor-stories/blob/master/f/README.md
(jwf, 14:42:43)
* Basic description of Contributor Stories now live on the README.
(jwf, 14:42:44)
* === [COMPLETE] "x3mboy File a ticket in CommOps Pagure about a new
podcast interview / episode on the CommOps team" === (jwf,
14:42:53)
* LINK: https://pagure.io/fedora-commops/issue/155 (jwf, 14:42:53)
* Figuring out the plan for the podcast; will discuss later in
meeting. (jwf, 14:42:53)
* === [COMPLETE] "bee2502 dhanesh95 jonatoni wesleyotugo x3mboy Review
the CommOps FAD event report draft this week, leave feedback in
CommOps ticket #125" === (jwf, 14:43:01)
* LINK:
https://communityblog.fedoraproject.org/fedora-commops-fad-2018/
(jwf, 14:43:01)
* FAD report is now published. (jwf, 14:43:02)
* Tickets (jwf, 14:43:35)
* LINK:
https://pagure.io/fedora-commops/issues?status=Open&tags=next+meeting
(jwf, 14:43:39)
* === Ticket #110: "Fedora Appreciation Week 2017" === (jwf,
14:43:55)
* LINK: https://pagure.io/fedora-commops/issue/110 (jwf, 14:43:55)
* LINK:
https://screenshots.firefox.com/NDyEhhKzQJ4WpXr4/etherpad.persephone.cloud
(jwf, 14:43:55)
* LINK:
https://communityblog.fedoraproject.org/?p=5376&preview=1&_ppp=dbe0f8ee96
(jwf, 14:44:06)
* Contributor Stories introduction publishes tomorrow morning. (jwf,
14:44:06)
* HELP: We can support the publishing of the post with social media
and posting to the announce- list. (jwf, 14:44:06)
* AGREED: Article publishes tomorrow and we will do some outreach to
build awareness. jwf covers Twitter/FB/G+, jonatoni covers
Instagram, bt0 covers the announce@ mailing list (jwf, 14:47:27)
* ACTION: jwf After May 1, promote "Introducing contributor stories"
CommBlog article on Twitter and round up others to help with FB / G+
(jwf, 14:47:57)
* ACTION: jonatoni After May 1, promote "Introducing contributor
stories" CommBlog article on Instagram (jwf, 14:48:07)
* ACTION: bt0 After May 1, promote "Introducing contributor stories"
CommBlog article by writing an email draft for announce(a)lists.fp.o
(jwf, 14:49:01)
* === Ticket #117: "How to create on-boarding guidelines for your
team" === (jwf, 14:51:12)
* LINK: https://pagure.io/fedora-commops/issue/117 (jwf, 14:51:12)
* Purpose is to write guidelines on creating effective onboarding
guidelines for Fedora sub-projects. We won't write guidelines for
someone, but we will try to give them a resource to do it well.
(jwf, 14:51:17)
* IDEA: Read through existing onboarding / joining guidelines for
different Fedora sub-projects / teams and identify similarities
(jwf, 14:53:58)
* AGREED: The end result of this task is a huge, so we need to break
it down into smaller, more manageable pieces (jwf, 15:09:52)
* dhanesh95 notes idea of including specific advice for different
*types* of teams, e.g. development and outreach (jwf, 15:10:14)
* IDEA: Keep it all to one document, but include a special section or
subheading with specific advice for development / programming teams
and SIGs, and then another for outreach-related teams, etc. (jwf,
15:10:44)
* AGREED: Next step is to split up the work into smaller pieces, and
make #117 into a master / tracking ticket (jwf, 15:12:32)
* ACTION: jwf Split up onboarding guidelines ticket (#117) into
smaller sub-tickets for different steps of work to produce the final
deliverable (jwf, 15:12:58)
* === Ticket #155: "Fedora Podcast Episode" === (jwf, 15:14:03)
* LINK: https://pagure.io/fedora-commops/issue/155 (jwf, 15:14:03)
* x3mboy expressed interest in a Fedora podcast interview with CommOps
team. Need to come up with a loose script and topics to cover during
the interview. (jwf, 15:14:03)
* HELP: Need help writing an outline of topics for the CommOps podcast
interview session with x3mboy (jwf, 15:14:03)
* IDEA: Did You Know fact for podcast: CommOps team members are split
across five continents! (jwf, 15:18:25)
* LINK:
https://communityblog.fedoraproject.org/fedora-commops-fad-2018/
(jwf, 15:19:59)
* LINK: https://public.etherpad-mozilla.org/p/FedoraDiversityPocast
(jwf, 15:21:16)
* ACTION: bt0 Create an outline / rough script of questions and topics
to cover in a Fedora podcast interview with x3mboy; request feedback
before Monday, May 14, 2018 meeting (jwf, 15:25:30)
* AGREED: Will determine a recording day and time after the outline /
script is approved (jwf, 15:25:49)
* Open floor (jwf, 15:26:47)
* bt0 will chair the next two meetings on Monday, May 7 and Monday,
May 14, in lieu of jwf's absence (jwf, 15:29:18)
Meeting ended at 15:32:22 UTC.
Action Items
------------
* commops New members, make sure you introduce yourself on the CommOps
mailing list [ https://fedoraproject.org/wiki/CommOps/Join ]
* jwf After May 1, promote "Introducing contributor stories" CommBlog
article on Twitter and round up others to help with FB / G+
* jonatoni After May 1, promote "Introducing contributor stories"
CommBlog article on Instagram
* bt0 After May 1, promote "Introducing contributor stories" CommBlog
article by writing an email draft for announce(a)lists.fp.o
* jwf Split up onboarding guidelines ticket (#117) into smaller
sub-tickets for different steps of work to produce the final
deliverable
* bt0 Create an outline / rough script of questions and topics to cover
in a Fedora podcast interview with x3mboy; request feedback before
Monday, May 14, 2018 meeting
Action Items, by person
-----------------------
* bt0
* bt0 After May 1, promote "Introducing contributor stories" CommBlog
article by writing an email draft for announce(a)lists.fp.o
* bt0 Create an outline / rough script of questions and topics to
cover in a Fedora podcast interview with x3mboy; request feedback
before Monday, May 14, 2018 meeting
* commops
* commops New members, make sure you introduce yourself on the CommOps
mailing list [ https://fedoraproject.org/wiki/CommOps/Join ]
* jonatoni
* jonatoni After May 1, promote "Introducing contributor stories"
CommBlog article on Instagram
* jwf
* jwf After May 1, promote "Introducing contributor stories" CommBlog
article on Twitter and round up others to help with FB / G+
* jwf Split up onboarding guidelines ticket (#117) into smaller
sub-tickets for different steps of work to produce the final
deliverable
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* jwf (226)
* dhanesh95 (33)
* bt0 (19)
* zodbot (10)
* jonatoni (9)
* fcommops-tg (7)
* commopsbot (6)
* algogator (0)
* commops (0)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
--
Cheers,
Justin W. Flory
jflory7(a)gmail.com
5 years, 5 months
[Self-Introduction] Abhishek Sharma
by Abhishek Sharma
Hello Everyone!
My Name is Abhishek and I am one of the Google Summer of Code students this
year for the Fedora Project. I will be working on the UX and Design of the
Fedora Community App under the guidance of my mentor, Kanika [a2batic].
I wish to update the project's weekly update on the Fedora Planet and was
wondering if someone could provide me CLA+1 access for the same.
Thank you!
Best,
Abhishek
5 years, 5 months
Fwd: [Release] pagure 4.0 and 4.0.1
by Justin W. Flory
Hot off the press! Pagure 4.0 coming soon. This is pretty big. :-) See
the changelog below from the Infrastructure mailing list.
This could be an awesome CommBlog article!
-------- Forwarded Message --------
Subject: [Release] pagure 4.0 and 4.0.1
Date: Thu, 26 Apr 2018 16:05:08 +0200
From: Pierre-Yves Chibon <pingou(a)pingoured.fr>
Reply-To: Fedora Infrastructure <infrastructure(a)lists.fedoraproject.org>
To: Fedora Infrastructure <infrastructure(a)lists.fedoraproject.org>
5 years, 5 months
