I've posted about this before but I just saw it again today and it
makes me sad. For whatever strange reason, Askbot comes with a "Closed
for the following reason the question is answered, right answer was
accepted" option. This is *completely* antithetical to the idea of
building a high-value store of useful information.
I guess it might make sense for a helpdesk-style system where we expect
each issue to be a one-off, but that's not generally the case here.
At the same time, I don't blame users/moderators for hitting this
button, because its very presence suggests that it's the right thing to
do. Can we:
a. reopen all questions closed this way
b. remove the option and make sure it doesn't come back?
Fedora Project Leader
In this debate, we also need to address the need for support of non English languages. We advertise Ask.fpo in a lot of place, but local communities have other place to discuss and give support to enduser. It would be great to discuss this someday.
I am a new joinee in the Fedora Infrastructure group.
IRC : vijbat
Current skillset: 1. Unix/Linux sysadmin/SAN/NAS/ESX/Netbackup/bash scripting
2. Basic familiarity with Oracle/MySQL/Nagios/Apache/Puppet/Cisco/F5
Looking to learn: 1. Python Scripting
2. DevOps technologies
3. Very much interested in how Fedora manages security aspects
4. Understanding Fedora Infrastructure setup
5. Would like to troubleshoot issues at some point
1. I havent uploaded my SSH public key yet. But at what point do we get access to any servers
Understand its not immediate, but just interested to know
2. Where can I find infrastructure diagrams/documents about the current setup
3. I see we use the ircchat #fedora-meeting, but do we do any conference calls too?
4. As Fedora is mostly community driven (understand its supported by RedHat), how does critical infrastrucure run.
Do we have dedicated sysadmins seperately to manage any sev1/sev2 faults.
And a lot more questions... But for now will hold on here..
Thanks for reading. Vijay
Resending so it hits the list.
On Thu, Oct 20, 2016, at 09:22 PM, Justin W. Flory wrote:
> On 10/20/2016 02:09 PM, Matthew Miller wrote:
> > On Thu, Oct 20, 2016 at 05:27:39PM -0000, Josh Boyer wrote:
> >> Should this be something that is sunset then? Or at a minimum widely
> >> advertised as needing community effort to keep active?
> > There are a handful of very active members who put in a lot of work and
> > effort; it isn't just a vacant lot full of weeds and bricks, which
> > would make the decision easy.
> > We never did get a "meta" site set up, so there's not really a great
> > place to have this discussion (which is why I'm having it here). I
> > guess I'll start a discussion there with the [meta] tag.
> As a thought to add to this, it would be nice to have a place for people
> interested in Ask Fedora to congregate and discuss. Before I was
> involved now, I had joined #fedora-ask in 2014 because I had considered
> looking into if I could help moderate or help the platform, but the
> channel was mostly fedmsg notifications.
> My point is, I think there may be people outside of the normal
> contributor periphery who may want to assist with Ask, but there's no
> effective means for people who wish to help to do so. This may not be
> relevant for Infrastructure, but some helpful steps I could see to
> bringing contributor focus into Ask is starting by providing a place and
> means for people who want to help to do so.
> One part of me says "there aren't enough contributors actively helping
> here to justify having it as a resource", but another part sees the
> great value in the fedmsg integration with Ask and how it does bring
> people and contributors *into* the project community.
Do we have activity statistics for the Ask site? Can we determine if
non-contributors are using it and actually getting help?
Should we make a push in the commblog for interested parties to come
forward? My gut feeling is that, as others have said in the thread, we
don't need any more bad open source copies making information hard to
find and growing weeds.
If there is an actual user community then we may choose to keep it
around and try to work harder on finding maintainers. If not, we can
give more serious thought to shutting it down, possibly as part of a
larger review of how we communicate with various platforms in general
(huge poop storm as someone said).
Good Morning Everyone,
One friday, late in the day, I cut a new release of pagure: 2.8
Here is the corresponding changelog:
* Fri Oct 21 2016 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 2.8-1
- Update to 2.8
- Fix the migration adding the close_status field to remove the old status
only at the end
- Fix the RTD and Force push hooks for the change in location of the plugins
- Fix creating new PR from the page listing the pull-requests
- Add the possibility for the user to edit their settings in their settings page
- Include the close_status in the JSON representation of an issue
- Load the close_status if there is one set in the JSON repsentation given
- Fix running the tests when EVENTSOURCE_SOURCE is defined in the
- Make the search case-insensitive when searching issues
- Fix the "cancel" button when editing a "regular" comment on a pull-request
- Remove the ``Content-Encoding`` headers from responses (Jeremy Cline)
- Fix creating the release folder for project with a namespace
- When sending email, make the user who made the action be in the From field
- When searching groups, search both their name and display name
- Create a Vagrantfile and Ansible role for Pagure development (Jeremy Cline)
- Made searching issue stop clearing status and tags filters (Ryan Lerch)
- Improve documentation (Bill Auger)
- Fix finding out the encoding of a file in git (Jeremy Cline)
- Fix making cross-project references using <project>#<id>
- Allow filter the list of commits for a certain user
- Ensure we disable all the submit button when clicking on one (avoid sending
- Do not always compute the list of diff commits
- Let's not assume PAGURE_CI_SERVICES is always there
- Allow html table to define their CSS class
- Add a link to the user on the commit list (Ryan Lerch)
- Change `Fork` button to `View Fork` on all pages of the project (tenstormavi)
- Enable some of the markdown extensions by default
- Fix mixed content blocked in the doc by not sending our user to google (Rahul
The new release was pushed on stg and prod.
We since found 4 annoying bugs that were either breaking the UI or making some
pages return 500 errors. All of these bugs have been hotfixed in prod and 3 of
the 4 pull-request merged.
Once the 4th PR is merged, I will cut a 2.8.1 release with these fixes and an
enhancement made by Vivek.
Sorry for the late notice of this new release.
A new release of pagure-importer is available from COPR
And it contains the following PR :
- tags improvements as per #37 (Vivek Anand)
- include enabling pagure tickets plugin instructions where all commands
are placed to double sure (Vivek Anand)
- Added tag to import all issues as private by default
- Add two-factor authentication to Github importer
- Let click handle the stdout
- Milestone support for github importer (Vivek Anand)
- Some make up in our code (Vivek Anand)
You are kindly invited to the meeting:
OSTree Multi Arch support in Bodhi on 2016-10-21 from 10:00:00 to 11:00:00 US/Eastern
The meeting will be about:
We will discuss how to get from where we are to having multi-arch support for OSTrees.