trac-git plugin updated on hosted1
by Jesse Keating
Please keep your eye out for any new failures with the git plugin. It
still doesn't handle file downloads, somebody is going to have to write
some code for that.
--
Jesse Keating
Fedora -- Freedom² is a feature!
15 years, 11 months
mdomsch vacation
by Matt Domsch
FYI, I'll be mostly offline starting Thursday 5/22 noon, back Tuesday
5/27. Mike and Seth know how to contact me in case of emergency.
Thanks,
Matt
--
Matt Domsch
Linux Technology Strategist, Dell Office of the CTO
linux.dell.com & www.dell.com/linux
15 years, 11 months
changes at planet fedora
by Seth Vidal
Hi all,
I’m making some changes with how we build up the list of folks/rss
feeds for the fedora planet. We’re making it more self-service and a bit
easier to maintain for the admin group (and specifically easier for me
to put up with). For all the people currently on the planet please
follow these instructions to make sure your feed stays on there:
http://skvidal.fedorapeople.org/docs/planet-addition.html
These instructions will be added to the wiki after the wiki migration
happens next week.
Let me know what problems you have, too.
thanks,
-sv
15 years, 11 months
New (beta) service, email to Trac tickets
by Jesse Keating
Over the past week I've spent some time getting email2trac setup on our
hosted environment so that projects can accept email for Trac tickets.
I have created an SOP for setting this up:
http://fedoraproject.org/wiki/Infrastructure/SOP/HostedEmail2Trac
If there are any questions related to this, please post them on list, or
in #fedora-admin
I'm going to use this for the rel-eng project (and to lesser extent the
pungi project as well) for a bit, before announcing this too loudly as a
new offering. I want to see how well it works and what concerns we
might have with a more public release of this service.
--
Jesse Keating
Fedora -- Freedom² is a feature!
15 years, 11 months
F10?
by Mike McGrath
So F9 is out the door and we had a very exciting last 6 months. Here's
the short list:
* FAS2
* /mnt/koji migration and deployment
* Backup system up and running
* Collaboration servers brought up (gobby and asterisk POC)
* UTC switch
The focus for this last release was mostly around sanity. Cleaning up
some configs, things like that. We actually did a very good job of that.
All in all I feel it was a good release. So my question to the team, what
would you all like to see over the next 6 months?
-Mike
15 years, 11 months
Fedora and CIA.vc
by Dimitris Glezos
I think this was discussed briefly in the past on IRC, having Fedora
listed on http://cia.vc/. CIA is "a real-time window into the open
source world", providing "Real-time open source activity stats" with
active projects, people, commits, etc.
It probably won't provide much added functionality (although its RSS
feeds are handy sometimes eg. [1]), but it'd be good having Fedora on
another contributor/project map. And with the diversity of the
projects hosted on Fedora Hosted, maybe this will bring more
contributors in.
We'll need to add the CIA client script to our versioning systems:
http://cia.vc/doc/clients/
-d
[1]: http://cia.vc/stats/project/kde/amarok
--
Dimitris Glezos
Jabber ID: glezos(a)jabber.org, GPG: 0xA5A04C3B
http://dimitris.glezos.com/
"He who gives up functionality for ease of use
loses both and deserves neither." (Anonymous)
--
15 years, 11 months
good morning infrastrucure list
by Matias Kreder
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi guys, I've subscribed since yesterday to this list. My name is Matias
Kreder, I'm from Buenos Aires, Argentina.
I am too interested in be a part of the fedora infrastructure team.
I've the RHCE and RHCS certifications, and part of the GSS (Global
Suppor Services) Latam Team.
I've 6 years of experience in linux, and open source technologies.
I hope that I can help in any any.
Best Regards!
Matias
P.D.: My english is not the best
- --
Matias E. Kreder
Support Engineer
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iEYEARECAAYFAkg0EeQACgkQTeno05BMVzt6HgCghW2+LM3w32yGAQuz7/22W7aA
9zwAn39cKAsQ+XYR7atGOkUu/AHNOo8B
=7Zoe
-----END PGP SIGNATURE-----
15 years, 11 months
Red Hat Bugzilla 3.2 Upgrade Beta 1
by John Poelstra
Hi,
I'm passing the following information on for the team that maintains the
Bugzilla instance Fedora runs in. It provides a peak into the upcoming
Bugzilla update and an opportunity to evaluate it in a test instance.
Check it out.
John
~~~~~~~~~~~~~~~~
Greetings,
The Red Hat Bugzilla team is happy to announce the first beta release
of the next version of Red Hat Bugzilla. The next version will be based
on the upcoming upstream 3.2 code base soon to be released.
https://partner-bugzilla.redhat.com
Along the way to the final release, we will be deploying several
beta releases that will be used for obtaining user feedback
and for finding bugs in our code changes. Red Hat has made substantial
customizations to our current 2.18 based Bugzilla system that have been
ported to the new release. Several of which we are working on having
them accepted
by the upstream community which will help in future bug fixes and
lower maintenance. We are also hoping to use the upgrade process as a
stepping stone to becoming more active in the future road map of Bugzilla
itself by providing help with bug fixes and enhancements and taking
part in future discussions.
Areas of focus for beta1:
Ajax optimizations:
Speedup one component/version/milestone population on the advanced query
screen due
to large volume of data for some products such as RHEL and Fedora.
Speedup of the show_bug.cgi page by reducing amount of HTML needed to
download
by not loading all components unless you want to change the value.
Needinfo actor support:
Using the flags functionality, we are able to specify whom additional
information
is being required of for a report. In the current 2.18 release a
combination of
a bug status called NEEDINFO and needinfo flag were used. In 3.2 only a
needinfo flag
is being used and the bug status will be removed.
Guided bug entry:
Modified stock guided bug entry page used to help non experts report bugs
with proper information.
UI enhancements:
Upstream Bugzilla developers have done extension work on streamlining
the show_bug.cgi page. The page should have a cleaner less cluttered
feel as well as show only editable fields for the values the user is
allowed
to change only. One of the more noticeable things is the removal of the
"Bug Status Change" area and moving it up to the basic bug information
area.
External bug references:
Ability to add links to outside bug trackers.
XMLRPC API:
The Red Hat Bugzilla system was one of the first Bugzilla installations
to utilize
XMLRPC extensively. Upstream as of 3.0 has a new framework for providing
Web Services
to clients to manipulate Bugzilla data. We have worked to help the
upstream to
add features to this framework to support similar functionality to what
we have
had in operation for some time. Some of the core functions are there
such as Bug.get(),
Bug.create(), Bug.search() and Bug.update() which can be used to do most
things needed.
Some of the operations available in our version are not yet available so
we are also
providing most of the old 2.18 API so that your applications and scripts
should continue
to work properly for the time being. Please try your scripts against the
test Bugzilla
system to make sure they are working properly. Let us know if there are
any errors
such as data not being returned in the proper format, certain methods
missing,
or bugs in general.
New methods available (Note: these are subject to change before final
release):
1. Bug.get() - Can be used to get all attributes of one or more bug
reports.
2. Bug.create() - Can create a new bug report in the system.
3. Bug.update() - Can update most attributes of one or more current
bug reports.
4. Bug.search() - Search the database for bugs matching search
criteria similar to advanced search UI.
Also supports quicksearch keywords and reloading of saved searches
saved in the Bugzilla UI.
5. Bug.get_activity() - Retrieve full history of one or more bug reports.
6. Bug.add_comment() - Can add a comment to a current bug report.
7. User.login() - Can take a username and password as parameters that
will return cookies that can be
used for all subsequent XMLRPC method calls. (Note: required to use
the new methods such as Bug.*)
8. User.create() - Create a new user if you have proper permissions.
9. User.get() - Get information about one or more current users if you
have proper permissions.
10. User.update() - Allows updating of email, real name, disabled, etc
for one or more current users.
11. Product.get_products() - Get information about one or more
products in Bugzilla.
12. Component.get() - Get information about one or more Bugzilla
components.
13. Component.create() - Create a new Bugzilla component for a
specific product.
14. Component.update() - Updated the attributes of one or more
Bugzilla components.
Old methods ported to 3.2 (for backwards compatibility):
1. bugzilla.runQuery()
2. bugzilla.getBug()
3. bugzilla.addIT()
4. bugzilla.getBugActivity()
5. bugzilla.nameToId()
6. bugzilla.login()
7. bugzilla.getBugSimple()
8. bugzilla.editComponent()
9. bugzilla.idToName()
10. bugzilla.getBugModified()
11. bugzilla.addComment()
12. bugzilla.updateFlags()
13. bugzilla.closeBug()
14. bugzilla.changeStatus()
15. bugzilla.updateCC()
16. bugzilla.getProdInfo()
17. bugzilla.createBug()
18. bugzilla.changeAssignment()
19. bugzilla.updateDepends()
20. bugzilla.getProdCompDetails()
21. bugzilla.addComponent()
22. bugzilla.updateMilestone()
23. bugzilla.getCompInfo()
24. bugzilla.getProductDetails()
25. bugzilla.getProductDetails()
26. bugzilla.userInfo()
27. bugzilla.addUser()
28. bugzilla.disableAccount()
The newer API is likely to change before the next release of upstream
Bugzilla
so we will be maintaining the older API during the time from 3.2 leading
up to
the next release. We do encourage people to try out the new API also so
as to
be ready for the eventual transition.
There are numerous other changes behind the scenes that we haven't
listed. The goal
is to make sure that functionality that people have come to expect in
2.18 is
possible in the new system.
There are also numerous new features/fixes that are part of the upcoming
3.2
release provided by the upstream Bugzilla community. For more detailed
information
on what has changed since the last release, check out the
[https://partner-bugzilla.redhat.com/page.cgi?id=release-notes.html
Release Notes].
The database is a recent snapshot of the live database so should be useful
for testing to make sure the information is displayed properly and
changeable.
Also with a full snapshot it is possible to test for any performance
related
issues. Email has been disabled so that unnecessary spam is not sent
out. So
feel free to make changes to bugs to verify proper working order.
We are asking for everyone to get involved as much as possible with
testing and feedback
on the beta releases to help us make this the most robust and stable
release possible.
We have done extensive work at laying out what we feel the requirements
are to maintain feature
parity with our current system as well as compiled a list of feature
enhancements
that people would like to see in the next release. Our goal is to deliver a
working bugzilla with the bare essential requirements similar to what is
currently being used
in our current 2.18 system. After that we will begin work on
enhancements as time and resources
permit. To view the final release requirements list please refer to our
[https://bugzilla.redhat.com/show_bug.cgi?id=406071 Bugzilla 3 Tracker].
Please file any enhancement requests or bug reports in our current
Bugzilla system
at [https://bugzilla.redhat.com bugzilla.redhat.com]. File them under
the Bugzilla
product and relevant component with the version 3.2. With everyones help
we can make
this a great release.
Thanks
The Red Hat Bugzilla Team
15 years, 11 months
MyFedora Documentation
by John (J5) Palmieri
http://fedoraproject.org/wiki/MyFedora/ is pointing to some new
documentation I started writing. Right now all I have is the plugin
design document (http://fedoraproject.org/wiki/MyFedora/PluginDesign)
but will be adding the plugin tutorial tomorrow and the widget tutorial
will be written the week before FudCon when Toshio and I lock ourselves
in a room and flesh out the design for the widget system that started at
the last FudCon. Others are encouraged to comment on the design and
send suggestions and I will be working during FudCon to get people
interested in developing content or working on the backends.
--
John (J5) Palmieri <johnp(a)redhat.com>
15 years, 11 months