Error 503 Backend fetch failed when login on wiki

[Zamir SUN]

Hi Infra team,

Now I failed to login on wiki. It reports such failure

Error 503 Backend fetch failed

Backend fetch failed
Guru Meditation:

XID: 4438215

Varnish cache server

I tried and I can still login via OpenID, for example, login to 
https://fedorahosted.org/fedora-badges/ .


HTH. Please take a look if it is infra issue.
--
Ziqian SUN (Zamir)
z...@fedoraproject.org
GPG : 1D86 6D4A 49CE 4BBD 72CF FCF5 D856 6E11 F2A0 525E
Want to know more about Fedora?
Visit https://fedoraproject.org/wiki/
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

Re: The Future of Ask Fedora (potentially: hosted by upstream)

[Zamir SUN]

Assuming we can make the money work out, what do you think about this?
Even if money is not a problem, I think paying for hosting this is not a 
wise idea.


And I suggest maybe someone can classify the issue/tasks into "easyfix" 
"medium" "troublesome" so that more people can involve in some bit.



On Wed, Dec 14, 2016 at 06:00:58PM -, Josh Boyer wrote:

However, I'm concerned about setting the precedent of paying to host
a service. The cost to Fedora to host it is not in machine time or
bandwidth, but in sysadmin and maintenance. Ideally, some of those


This is a good point that I hadn't considered. It wasn't really the
hosting per se that I'm interested in, but getting the service overall
into a better place, and this seemed like a possible way to do that.
But, if we were to try to directly sponsor every upstream project on
which we depend in some way, we'd use up not just our budget but pretty
much all the money in the world.



same passionate Fedora Ask community members would step forward to
help run the site by becoming part of FI, even if only to service
Ask.


Okay, so needs here are:


Sysadminy/packager stuff:

  - some more hands on deck for routine administration

  - updating to newest codebase
- package as RPM?
- update ansible playbooks

  - reconfiguration on site itself to better match high-load site


Developery stuff (in my rough order of priority)

  - Fix the "closed: answered" reason (as I've discussed before)

  - Make duplicate handling useful — include voting system

  - Creation of a real "meta" subsite

  - A flagging system for issues beyond "offensive"

  - Insight into things like most viewed, most duplicated, and most
upvoted questions, so we can consider creating Fedora Magazine
articles and more formal documentation for those things.

  - Rework notifications so they more useful (broken down by
categories, not punishing users for helping copy-edit questions)

  - Ability to put questions in need of help (for example, unclear
with not enough information) on hold rather than closing outright

  - Community review queues a la Stack Exchange

  - Tie in better to Fedora Badges (possibly completely disable
integrated badges)

This doesn't all need to be instant, but I'd like to be moving towards
it





--
Ziqian SUN (Zamir)
z...@fedoraproject.org
GPG : 1D86 6D4A 49CE 4BBD 72CF FCF5 D856 6E11 F2A0 525E
Want to know more about Fedora?
Visit https://fedoraproject.org/wiki/
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

Re: The Future of Ask Fedora (potentially: hosted by upstream)

[charles profitt]

On Wed, 2016-12-14 at 15:42 -0500, Matthew Miller wrote:

> Okay, so needs here are:
> 
> 
> Sysadminy/packager stuff:
> 
>   - some more hands on deck for routine administration
>    
>   - updating to newest codebase
> - package as RPM?
> - update ansible playbooks
> 
>   - reconfiguration on site itself to better match high-load site
> 
> 
> Developery stuff (in my rough order of priority)
> 
>   - Fix the "closed: answered" reason (as I've discussed before)
> 
>   - Make duplicate handling useful — include voting system 
> 
>   - Creation of a real "meta" subsite
> 
>   - A flagging system for issues beyond "offensive"
> 
>   - Insight into things like most viewed, most duplicated, and most
> upvoted questions, so we can consider creating Fedora Magazine
> articles and more formal documentation for those things.
> 
>   - Rework notifications so they more useful (broken down by
> categories, not punishing users for helping copy-edit questions)
>   
>   - Ability to put questions in need of help (for example, unclear
> with not enough information) on hold rather than closing outright
> 
>   - Community review queues a la Stack Exchange
> 
>   - Tie in better to Fedora Badges (possibly completely disable
> integrated badges)
> 
> This doesn't all need to be instant, but I'd like to be moving
> towards
> it

I like the idea of trying to work inside our community to seek people
to help be sysadmins for AskFedora and to be developers.

I might be willing to take on some of the administrative tasks, but I
have no idea how to get started nor how much of a time commitment this
would be.

Charles


signature.asc
Description: This is a digitally signed message part
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

Re: The Future of Ask Fedora (potentially: hosted by upstream)

[charles profitt]

On Wed, 2016-12-14 at 12:15 -0500, Matthew Miller wrote:
> Ask Fedora is one of our primary user-facing support resources. It's
> reasonably successful, with over 18,000 questions, with almost 80% of
> those having at least some answer. It has a small but active and
> passionate community.

ask type communities can be an incredible resource for a community. I
was very active with AskUbuntu before converting to Fedora.

> On the other hand, I've heard from the infrastructure team that it's
> taking an increasing amount of time just to keep the service running,
> and making improvements is out of the question. We're having trouble
> keeping up with things like keeping the software on the recent
> version, let alone advancing new ideas.


> Since this is such an important thing for users, I think we need an
> improvement. I asked the community what to do
>  king-and-whats-the-future/>
> and the top-voted response is from the upstream author, who has
> offered
> to host the site for $250/month, including 6 hours of development
> time.
> 
> Assuming we can make the money work out, what do you think about
> this?

It is a small community when compared with AskUbuntu that has 249,575
answers. I personally found it difficult to get started with AskFedora
and have not revisited the site. I think if we make a commitment to
paying for someone to host the site that we need to make an effort to
make it easier for more users to contribute to the site.

Charles

signature.asc
Description: This is a digitally signed message part
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

[release] fedmsg_meta_fedora_infrastructure: 0.17.7

[Pierre-Yves Chibon]

0.17.7
--

Pull Requests

- (@pypingou)   #383, Perform 26 smaller queries instead of 1 to retrieve 
the entire list of users
  https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/pull/383
- (@pypingou)   #396, Fix something we faced in FMN stg, copr messages 
where the agent is None
  https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/pull/396
- (@vivekanand1101) #397, Adjust after diff access levels in pagure
  https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/pull/397
- (@vivekanand1101) #398, Add support for project.group.added and 
project.group.access.updated …
  https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/pull/398
- (@hroncok)#400, When copr repo belongs to a group, alter the link
  https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/pull/400
- (@puiterwijk) #401, Add pungi-ostree messages
  https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/pull/401
- (@tyll)   #405, Use https, mention libffi-devel
  https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/pull/405
- (@AdamWill)   #408, update openQA processor and tests for comment messages
  https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/pull/408
- (@ralphbean)  #403, Handle new koji rpm.sign message format.
  https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/pull/403
- (@pypingou)   #409, Include the namespace if there is one and fork/ if it 
is one
  https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/pull/409

Commits

- c7802467d Perform 26 smaller queries instead of 1 to retrieve the entire list 
of users
  
https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/commit/c7802467d
- 3098d58ee Add missing import of the string module
  
https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/commit/3098d58ee
- 03c1a2bca 0.17.6
  
https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/commit/03c1a2bca
- ef0af85bf Small improvements on user iteration.
  
https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/commit/ef0af85bf
- 1c7cd8eb5 This is really a response, not a request.
  
https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/commit/1c7cd8eb5
- b9bd9d90b Fix something we faced in FMN stg, copr messages where the agent is 
None
  
https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/commit/b9bd9d90b
- 0a411fd6e pagure has access levels now, update: add user to project, update 
user access level to a project
  
https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/commit/0a411fd6e
- 109b51726 pagure != anitya :o
  
https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/commit/109b51726
- 63dc77123 adjust tests for adding of user to a project on pagure after diff 
access levels
  
https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/commit/63dc77123
- 5641323e2 add tests for update of access level for a user in pagure
  
https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/commit/5641323e2
- 75483d2b1 Add support for project.group.added and 
project.group.access.updated for pagure msgs
  
https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/commit/75483d2b1
- d96803321 When copr repo belongs to a group, alter the link
  
https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/commit/d96803321
- b304612b0 Make sure user is a str before checking how it starts
  
https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/commit/b304612b0
- c557bc742 Test case for Copr group repo link
  
https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/commit/c557bc742
- affa60ac5 Save the actual msg
  
https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/commit/affa60ac5
- d7832a38c Add expected title and subtitle for #400
  
https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/commit/d7832a38c
- aa65a8c9c Travis CI: Upgrade pip and setuptools
  
https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/commit/aa65a8c9c
- 39d81cb2e Add pungi-ostree messages
  
https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/commit/39d81cb2e
- fb4e189ac Handle new koji rpm.sign message format.
  
https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/commit/fb4e189ac
- 44756cd53 Use https, dnf, mention libffi-devel
  
https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/commit/44756cd53
- a02297357 update openQA processor and tests for comment messages
  
https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/commit/a02297357
- 4f1f9134e Include the namespace if there is one and fork/ if it is one
  
https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/commit/4f1f9134e


Builds are in progress, soon to land in the infra side tag :)

Pierre
___
infrastructure mailing list -- 

Re: fedpkg import: Could not execute import_srpm

[Jun Aruga]

Hi Tomasz,

> Try
> 
>   dnf --enablerepo=updates-testing upgrade fedpkg
> 
> And, if it works fine for you, please provide positive karma at
> https://bodhi.fedoraproject.org/updates/FEDORA-2016-a383ccbf57

Thanks! It works fine for me! I provided positive karma!

Jun Aruga


- Original Message -
> From: "Tomasz Torcz" 
> To: infrastructure@lists.fedoraproject.org
> Sent: Thursday, December 15, 2016 10:18:27 PM
> Subject: Re: fedpkg import: Could not execute import_srpm
> 
> On Thu, Dec 15, 2016 at 03:31:42PM -0500, Jun Aruga wrote:
> > Thanks for the information!
> > 
> > 
> > $ sudo dnf upgrade fedpkg --refresh
> > 
> > $ rpm -qa fedpkg
> > fedpkg-1.25-1.fc24.noarch
> > 
> > Then I have checked several "updates" repos too.
> > 
> > So, maybe I need to wait to use 1.26?
> 
> Try
> 
>   dnf --enablerepo=updates-testing upgrade fedpkg
> 
> And, if it works fine for you, please provide positive karma at
> https://bodhi.fedoraproject.org/updates/FEDORA-2016-a383ccbf57
> 
> --
> Tomasz TorczOnly gods can safely risk perfection,
> xmpp: zdzich...@chrome.pl it's a dangerous thing for a man.  -- Alia
> ___
> infrastructure mailing list -- infrastructure@lists.fedoraproject.org
> To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
> 
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

Re: The Future of Ask Fedora (potentially: hosted by upstream)

[Vít Ondruch]

Dne 15.12.2016 v 17:13 Matthew Miller napsal(a):
> On Thu, Dec 15, 2016 at 10:57:44AM -0500, Stephen John Smoogen wrote:
>> Which loops us back to the original. The upstream is trying to make
>> this an open source product where they are paid for their time to work
>> on this by organizations who are using said product.
>  which is fine, but Fedora isn't really in a position to sponsor
> work in that way.
>

Can Red Hat hire him? ;)


V.
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org