Front page text
by Tom Callaway
To replace the old placeholder text:
FIXME: This is not correct wording. Fedora Community is a place where
Fedora package maintainers can collaborate on building and maintaining
their packages. Logging into your Fedora account in Fedora Community
allows you to keep up with your packages and to keep track of your
friends’ packages as well.
I propose:
Fedora Community provides a window into the Fedora distribution,
leveraging the power of Fedora's Account System, Bodhi, Bugzilla, Koji,
and PackageDB into a single user-friendly website. Built entirely with
Free Software such as Moksha and TurboGears 2, Fedora Community is
designed to simplify Fedora workflows and bring transparency to Fedora
processes.
Thoughts?
~spot
14 years, 11 months
Fedora Community Update
by Luke Macken
Problems solved
---------------
#227 - Package Maintenance > Updates > All Packages > Overview: dashboard
counts are all 0, incorrect
#219 - Added status column to Package -> Updates grid
#197 - Order architectures in our downloads list, and hide arches with
no downloads
#194 - Ordered releases in the pkg connector
Fixed a bug in the KojiConnector.call_get_latest_changelog method that
caused problems when viewing builds that have been garbage collected in
Koji.
Cranked through more TG2 packaging
#226 - Detect security bugs add the 'security-bug' css class to the
rows. Also, flag security and obsolete updates as well, and make them
stand out in the grids.
We now cache the first 5 pages of every bug grid.
We now also cache our bug # list for each package. This shaves off 1
(out of 2) bugzilla requests per grid action, on an uncached grid or on
pages 6+
#218 - Moved to __future__. ViewVCS scraping comes later
#173 - Add the few fas icon next to the group membership links
#222 Package Details > Maintenance Tools > Updates grid to match mockup
#181 - Use Moksha's new DateTimeDisplay.age(general=True) argument,
which works similar to what is described in ticket. The distance in
time displays now match the mockups.
Add a BodhiConnector._get_update_details method and inject
'details' into update
- If the update is stable, the details will be the updateid and the date pushed.
- If the update is obsolete, it will link to the update that obsoleted it
Race condition in the grids.
Fixed by implementing the moksha.lib.helpers.when_ready method that
wraps our javascript calls around $(document).ready(function(){ });
In process
----------
#254 - Spots "My Packages" widget returns *all* details about *all* of
his packages, which amounts to almost 1MB of data.
Looks to be a pagination issue, probably due to the recent TurboGears 1.0.8
upgrade. Ball is in Toshio's court:https://fedorahosted.org/packagedb/ticket/148
Update/build action buttons are currently 90% refactored, and just need
to be polished and tested.
#153 - Timezone support has been added to the Moksha DateTimeDisplay object,
and now just needs to be utilized throughout FComm.
#177 - New multi-build update mockup will also fix #139, and should not be
very difficult to implement.
14 years, 11 months
FComm update
by John (J5) Palmieri
We are rolling now. Closed my most major bugs and close to closing another:
Closed:
* package details > builds: changelog dropdown widget should be implemented - https://fedorahosted.org/fedoracommunity/ticket/210 - you now will see a changelog link on each build and it even works for failed and in progress builds
* bad url ref page (fail whale/faildora) - https://fedorahosted.org/fedoracommunity/ticket/234 - it isn't pretty but it works. I even found some bad links from the package list with it
Updated:
* title tags not useful - https://fedorahosted.org/fedoracommunity/ticket/149 - last tab wins with packages and user names also showing up. I may have also missed some places so I haven't closed this yet
* right hand nav for package list - https://fedorahosted.org/fedoracommunity/ticket/182 - I did what I could for now and moved this to __future__ since we need work on the backends to look exactly like the mockups. Added the Packages I Own, Maintain and watch pages
I have a couple of more feature requests on the critical list but I think they might be hard to do/may need to be punted. I'm going to work on some of Luke's critical list to get the most important ones out of the way and then revisit the features.
--
John (J5) Palmieri
Software Engineer
Red Hat, Inc.
14 years, 11 months
