| |
@@ -23,10 +23,10 @@
|
| |
|
| |
1. link:https://fedoraproject.org/wiki/Foundation[The Foundation]
|
| |
2. http://docs.fedoraproject.org/en-US/index.html[Fedora Documentation
|
| |
- (Users/ Contributors)]
|
| |
+ (Users/ Contributors)]
|
| |
3. link:https://fedoraproject.org/wiki/Communicate/IRCHowTo[How to work with IRC?]
|
| |
- https://fedoramagazine.org/begginers-guide-to-irc[Beginner's Guide to
|
| |
- IRC]
|
| |
+ https://fedoramagazine.org/begginers-guide-to-irc[Beginner's Guide to
|
| |
+ IRC]
|
| |
4. link:https://fedoraproject.org/wiki/FAS[Fedora Account System]
|
| |
5. link:https://fedoraproject.org/wiki/Development[Development]
|
| |
|
| |
@@ -98,10 +98,10 @@
|
| |
|
| |
* Implement tinykdump daemon to be included in Fedora.
|
| |
* Submit kernel patches for reserving kdump memory at run-time for
|
| |
- community review and inclusion.
|
| |
+ community review and inclusion.
|
| |
* Currently, pstore only log kernel messages for panic and Oops. Patches
|
| |
- are needed to support logging of kdump kernel and initramfs console
|
| |
- output.
|
| |
+ are needed to support logging of kdump kernel and initramfs console
|
| |
+ output.
|
| |
|
| |
[[improve-fedora-review]]
|
| |
=== Improve Fedora Review
|
| |
@@ -128,13 +128,13 @@
|
| |
|
| |
* Make Fedora Review PEP8 compliant, fix its current test cases
|
| |
* Help running Fedora Review regularly for existing packages e.g.,
|
| |
- updating the Jenkins continuous builds and/or integrate it into
|
| |
- Taskotron
|
| |
+ updating the Jenkins continuous builds and/or integrate it into
|
| |
+ Taskotron
|
| |
* Add static code checker support to Fedora Review (e.g. with
|
| |
- https://git.fedorahosted.org/git/csmock.git[csmock])
|
| |
+ https://git.fedorahosted.org/git/csmock.git[csmock])
|
| |
* Build a web service mockup supporting the review process
|
| |
- http://fedoraproject.org/wiki/Package_Review_Process[1] replacing
|
| |
- current bugzilla workflow.
|
| |
+ http://fedoraproject.org/wiki/Package_Review_Process[1] replacing
|
| |
+ current bugzilla workflow.
|
| |
|
| |
[[enhance-fedora-build-setup]]
|
| |
=== Enhance Fedora build setup
|
| |
@@ -159,21 +159,21 @@
|
| |
_Notes:_ Rough roadmap:
|
| |
|
| |
* Make select https://fedorahosted.org/rel-eng/[releng scripts] PEP8
|
| |
- compliant/python3 ready
|
| |
+ compliant/python3 ready
|
| |
* Make other python tools PEP8 compliant, python3 ready:
|
| |
** https://fedorahosted.org/fedpkg/[fedpkg]
|
| |
** https://git.fedorahosted.org/cgit/mash/[mash]
|
| |
** https://fedorahosted.org/rpkg/[rpkg]
|
| |
* Become familiar with the Fedora packaging workflow, maybe by packaging
|
| |
- some software
|
| |
+ some software
|
| |
* Learn how to interface koji and write a script to get a mapping of git
|
| |
- commit ID to package build (name, version, release)
|
| |
+ commit ID to package build (name, version, release)
|
| |
* Write a koji plugin to enforce that pkgs can be only built from the
|
| |
- right GIT branch for each build target (might need improvements to
|
| |
- koji's plugin interface as well):
|
| |
- https://fedorahosted.org/rel-eng/ticket/5843
|
| |
+ right GIT branch for each build target (might need improvements to
|
| |
+ koji's plugin interface as well):
|
| |
+ https://fedorahosted.org/rel-eng/ticket/5843
|
| |
* Write a fedmsg service/cronjob to regularly tag sucessful builds in
|
| |
- GIT: https://fedorahosted.org/rel-eng/ticket/5856
|
| |
+ GIT: https://fedorahosted.org/rel-eng/ticket/5856
|
| |
* Help with koji2
|
| |
|
| |
[[improve-sigul-signing-server]]
|
| |
@@ -203,30 +203,30 @@
|
| |
_Notes:_ Rough roadmap:
|
| |
|
| |
* To test whether everything works, a test instance needs to be setup.
|
| |
- This is rather complex because it requires interaction with koji. Maybe
|
| |
- it is possible to add a test instance to Infrastructure that can use the
|
| |
- koji staging system, but the latter is not fully functional right now.
|
| |
+ This is rather complex because it requires interaction with koji. Maybe
|
| |
+ it is possible to add a test instance to Infrastructure that can use the
|
| |
+ koji staging system, but the latter is not fully functional right now.
|
| |
* Debug why sigul hangs sometimes when using the
|
| |
- https://git.fedorahosted.org/cgit/sigul.git/tree/src/client.py#n1090[sign-rpms]
|
| |
- command (called by `--batch-size` greater than one with
|
| |
- `sigulsign_unsigned.py`
|
| |
+ https://git.fedorahosted.org/cgit/sigul.git/tree/src/client.py#n1090[sign-rpms]
|
| |
+ command (called by `--batch-size` greater than one with
|
| |
+ `sigulsign_unsigned.py`
|
| |
* Enable sigul to process multiple tasks at once, e.g. sign for multiple
|
| |
- releases or architectures at once.
|
| |
+ releases or architectures at once.
|
| |
* Fix other bugs/issues, examples:
|
| |
** Currently http://linux.die.net/man/8/logrotate[logrotate] does not
|
| |
- make sigul properly re-open its logfiles, which is why sigul does not
|
| |
- log to the new logfile after rotation. This needs to be fixed in sigul
|
| |
+ make sigul properly re-open its logfiles, which is why sigul does not
|
| |
+ log to the new logfile after rotation. This needs to be fixed in sigul
|
| |
** The GPG defaults in sigul might not be up-to-date, they should be
|
| |
- reviewed and improved if necessary
|
| |
+ reviewed and improved if necessary
|
| |
** Add support for e.g. signing and revoking GPG keys, to build a local
|
| |
- web of trust between https://getfedora.org/keys/[Fedora release keys]
|
| |
+ web of trust between https://getfedora.org/keys/[Fedora release keys]
|
| |
|
| |
Ressources:
|
| |
|
| |
* https://git.fedorahosted.org/cgit/releng/tree/scripts/sigulsign_unsigned.py[Script
|
| |
- used by rel-eng to run sigul]
|
| |
+ used by rel-eng to run sigul]
|
| |
* https://git.fedorahosted.org/cgit/sigul.git/tree/doc/protocol-design.txt[Protocol
|
| |
- description]
|
| |
+ description]
|
| |
|
| |
[[askfedora-uxui-functionality-overhaul]]
|
| |
=== AskFedora UX/UI & Functionality Overhaul
|
| |
@@ -292,35 +292,35 @@
|
| |
control, and intended to be part of a FLOSS design suite that includes
|
| |
|
| |
* http://sparkleshare.org[Sparkleshare] - a git-backed, Dropbox like
|
| |
- system that will automatically check in and push files in project
|
| |
- directly to a shared git repo
|
| |
+ system that will automatically check in and push files in project
|
| |
+ directly to a shared git repo
|
| |
* https://github.com/garrett/magicmockup[Magic Mockup] - a javascript
|
| |
- library you can insert into an SVG of mockups to enable interactive,
|
| |
- click-through mockups
|
| |
- (http://blog.linuxgrrl.com/2011/08/12/interactive-svg-mockups-with-inkscape-javascript/[see
|
| |
- a demo here]
|
| |
+ library you can insert into an SVG of mockups to enable interactive,
|
| |
+ click-through mockups
|
| |
+ (http://blog.linuxgrrl.com/2011/08/12/interactive-svg-mockups-with-inkscape-javascript/[see
|
| |
+ a demo here]
|
| |
* http://inkscape.org[Inkscape] is our preferred design tool of choice
|
| |
|
| |
Last year, two GSoC students worked on a number of critical improvements
|
| |
to GlitterGallery, but there is still plenty of work to be done.
|
| |
|
| |
* Public gallery of works; currently the app requires a user to login
|
| |
- and to follow other users before they can see work other than their own.
|
| |
- They can also view direct links to works. A public gallery can be used
|
| |
- to browse and explore works without having to be logged in.
|
| |
+ and to follow other users before they can see work other than their own.
|
| |
+ They can also view direct links to works. A public gallery can be used
|
| |
+ to browse and explore works without having to be logged in.
|
| |
* Better design suite integration, which could mean better support for
|
| |
- local editing with SparkleShare; Inkscape integration through an
|
| |
- extension; and/or support for creating and sharing interactive SVGs with
|
| |
- Magic Mockup
|
| |
+ local editing with SparkleShare; Inkscape integration through an
|
| |
+ extension; and/or support for creating and sharing interactive SVGs with
|
| |
+ Magic Mockup
|
| |
* Better commenting - the current commenting system is basic, and
|
| |
- there's lots of ways it could be improved, including thread support,
|
| |
- pingback support, the ability to reference a specific region of a design
|
| |
- in a comment
|
| |
+ there's lots of ways it could be improved, including thread support,
|
| |
+ pingback support, the ability to reference a specific region of a design
|
| |
+ in a comment
|
| |
* External issue tracking - Glitter Gallery has an integrated issue
|
| |
- tracker, but it would be useful to also be able to integrate with
|
| |
- external bug/issue trackers such as GitHub and Bugzilla.
|
| |
+ tracker, but it would be useful to also be able to integrate with
|
| |
+ external bug/issue trackers such as GitHub and Bugzilla.
|
| |
* Enhanced history view - (see
|
| |
- https://github.com/glittergallery/GlitterGallery/issues/187)
|
| |
+ https://github.com/glittergallery/GlitterGallery/issues/187)
|
| |
* Your own ideas
|
| |
|
| |
_Knowledge prerequisites:_ git, Ruby on Rails, front-end (HTML/CSS/JS)
|
| |
@@ -537,17 +537,17 @@
|
| |
|
| |
* Show a clear overview for patches in Fedora for a certain package
|
| |
** Link to bugs that were mentioned, extract key information from the
|
| |
- bug
|
| |
+ bug
|
| |
* Allow to get notifications for new patches, e.g. via fedmsg
|
| |
* Allow to get information about patches for the package in other
|
| |
- distros
|
| |
+ distros
|
| |
* Try to figure out if patches are already upstream
|
| |
* ...
|
| |
|
| |
Rough potential roadmap:
|
| |
|
| |
* Get the debian patch tracker running on a test system, maybe with some
|
| |
- example debian packages
|
| |
+ example debian packages
|
| |
* Port it for one example Fedora package
|
| |
* Port it to a modern web framework such as Flask or Pyramid
|
| |
* Make sure it is PEP8 compliant
|
| |
@@ -560,14 +560,14 @@
|
| |
|
| |
* Target platform is RHEL/CentOS7 with EPEL
|
| |
* All dependencies should be available on the target platform as RPM
|
| |
- packages or possible to be packaged (e.g. requiring newer versions of
|
| |
- packages already included in the target platform might not be easily
|
| |
- possible)
|
| |
+ packages or possible to be packaged (e.g. requiring newer versions of
|
| |
+ packages already included in the target platform might not be easily
|
| |
+ possible)
|
| |
* It needs to be possible to package the final project for Fedora/EPEL,
|
| |
- i.e. there may not be bundled libraries included
|
| |
+ i.e. there may not be bundled libraries included
|
| |
* The code needs to be PEP8 compliant and contain proper docstrings
|
| |
* Proper automtatic tests should be included to allow meaningful
|
| |
- continuous integration
|
| |
+ continuous integration
|
| |
|
| |
Recommended basic knowledge:
|
| |
|
| |
@@ -655,7 +655,7 @@
|
| |
Helpful documentation:
|
| |
|
| |
* link:https://fedoraproject.org/wiki/Using_Mock_to_test_package_builds[Using Mock to test package
|
| |
- builds]
|
| |
+ builds]
|
| |
|
| |
[[enhance-postgresql-gssapi-support]]
|
| |
=== Enhance PostgreSQL GSSAPI Support
|
| |
in the internationalization system of our docs, the tool po4a we use to convert asciidoc files into pot displays three lines of warning for each missing indentation.
most of the time it is cosmetic issues in adoc (like here), but sometimes it's po4a bugs that I want to see
this PR has no impact on your rendering, it is fully cosmetic