Re: contingency plan for the failed-to-build spins/labs?

[Dennis Gilmore]

On Monday, June 20, 2016 12:48:03 PM CDT Matthew Miller wrote:
> On Mon, Jun 20, 2016 at 09:32:23AM -0500, Dennis Gilmore wrote:
> > Jam failed due to package issues, its package set was not installable, dnf
> > aborted the transactionso anaconda failed to install, it will be getting
> > removed and will have to follow the process for a new spin if it is to
> > ever
> > come back, same as any spin that misses the boat, however given that SoaS
> > and
> Okay, that's fair for Jam.
> 
> > As we move into a more automated way doing one off things like this
> > is going to get harder and harder to accomodate and do anything
> > about. Relaistically at this point doing anything here is more up to
> 
> This seems backwards to me. As we get more complicated and develop
> automation to assist with that complication, we need to get _more_
> flexible, not less. I'd love for Spins to be able to ship when the SIG
> for each one determines that their thing is ready - if someone wants to
> fix up Jam, release it next month or whatever.

We are not resourcesd or setup for something like that. We would need some 
number of new resources approaching on probably 4-5 maybe more people in order 
to do anything. We are doing what we can with the resources we have. In order 
to do more and do it faster something has to give. that something today is the 
hacks to do thinsg off to the side.


> For that matter, it'd be nice to have the option for the main Editions
> - if there's something that only affects Workstation or Server, don't
> hold up the other (or the underlying release) for it.
> 
> From a PR point of view, the releases don't drive press like they used
> to - I think we'd actually be better served by more, smaller
> announcements. From a user adoption point of view, releases aren't the
> driver either - data shows a download spike for new releases, but
> overall the total Fedora users curve grows independently from that.
> People come for whatever release is current and don't generally wait
> for the splash of the next one.

What you are talking about is essentailly forking the distribution into 
multiple distributions, Which needs a lot more resources. there is additional 
legal complications over things like source matching that we ignore today due 
to having the Everything repo with the matching sources. we would have to make 
many more repositoryies, extra stress and load on infrastructure and mirrors, 
release engingeering, QA, and many other parts of the ecosystem.  I think we 
need to talk because there is only so much we can do given what resourcing we 
have.

Dennis
--
websites mailing list
websites@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/websites@lists.fedoraproject.org

Re: Introduction: Liam Murphy

[Robert Mayr]

2016-06-17 16:00 GMT+02:00 Liam Murphy :

> Hello websites team!
>
> My name is Liam Murphy.
>
> I've only been using Linux and been a FOSS advocate for around a year
> now, and some months ago I started using Fedora for my daily work.
>
> I am 18 years old, and will be starting college this fall for Computer
> Science.
>
> Currently I am comfortable with HTML, CSS, and WordPress. I am iffy with
> JavaScript and Ruby on Rails. I am working on getting better with C, and
> then C++.
>
> I also love talking to people, so at some point would like to go for
> Ambassador,  but that is likely down the road.
>
> My focus on talking to people, would be exposing other people around my
> age to Fedora and FOSS in general.
>
> I have only made on contribution to the websites team thus far, just a
> minor url bug in the documentation. But I hope to do more.
>
> Thanks for your time reading, and I look forward to talking/working with
> you all!
>
> Cheers,
>
> Liam Murphy
> --
> websites mailing list
> websites@lists.fedoraproject.org
>
> https://lists.fedoraproject.org/admin/lists/websites@lists.fedoraproject.org


Hi Liam,
sorry for the late reply, and welcome.
You can easily setup your system and start building the websites locally,
even do pull requests. I guess you followed our join page, please ask if
you have any doubt or questions about our workflow.
A boilerplate response will give you the main steps to follow>
https://fedoraproject.org/wiki/Websites/Boilerplate#Inquiry_regarding_how_to_join_the_websites_team

Just pass by in #fedora-websites and say hello, I'm looking forward to see
you soon.
Kind regards.

-- 
Robert Mayr
(robyduck)
--
websites mailing list
websites@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/websites@lists.fedoraproject.org

Re: [fedora-websites] #244: Create system for automated screenshots capture

[fedora-websites]

#244: Create system for automated screenshots capture
-+
 Reporter:  jreznik  |   Owner:  webmaster
 Type:  enhancement  |  Status:  closed
 Priority:  minor|   Milestone:
Component:  General  |  Resolution:  wontfix
 Keywords:   |  Blocked By:
 Blocking:   |
-+
Changes (by robyduck):

 * status:  new => closed
 * resolution:   => wontfix


Comment:

 We have just 6 screenshots right now and we ask the owners if we need a
 new one. This ticket is rather old, feel free to reopen it.

-- 
Ticket URL: 
fedora-websites 
Fedora Website Team's Trac instance
--
websites mailing list
websites@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/websites@lists.fedoraproject.org

Re: [fedora-websites] #397: Write a blurb for labs/spins which failed the final compose

[fedora-websites]

#397: Write a blurb for labs/spins which failed the final compose
--+
 Reporter:  robyduck  |   Owner:  webmaster
 Type:  task  |  Status:  new
 Priority:  critical  |   Milestone:  ASAP
Component:  General   |  Resolution:
 Keywords:  easyfix   |  Blocked By:
 Blocking:|
--+

Comment (by robyduck):

 SoaS and Design are pointing to the nightlies now, but I wrote just some
 hardcoded code. Let's create a template for it and add it to the
 spins/labs, in order to use it easily when needed.

-- 
Ticket URL: 
fedora-websites 
Fedora Website Team's Trac instance
--
websites mailing list
websites@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/websites@lists.fedoraproject.org

Re: [fedora-websites] #395: Beta 24 broken link for 32 bit live workstation iso

[fedora-websites]

#395: Beta 24 broken link for 32 bit live workstation iso
--+
 Reporter:  drummike  |   Owner:  webmaster
 Type:  defect|  Status:  closed
 Priority:  minor |   Milestone:
Component:  General   |  Resolution:  invalid
 Keywords:|  Blocked By:
 Blocking:|
--+
Changes (by robyduck):

 * status:  new => closed
 * resolution:   => invalid


Comment:

 This is a redirect, you should report the mirror giving you this error.
 Sorry for the late reply, I guess you do not need it anymore, as we
 released F24 today.

-- 
Ticket URL: 
fedora-websites 
Fedora Website Team's Trac instance
--
websites mailing list
websites@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/websites@lists.fedoraproject.org

Re: [fedora-websites] #391: Prepare websites for F24 release

[fedora-websites]

#391: Prepare websites for F24 release
--+
 Reporter:  robyduck  |   Owner:  webmaster
 Type:  task  |  Status:  closed
 Priority:  major |   Milestone:  Fedora 24
Component:  General   |  Resolution:  fixed
 Keywords:|  Blocked By:  371, 369, 362
 Blocking:|
--+
Changes (by robyduck):

 * status:  new => closed
 * resolution:   => fixed


-- 
Ticket URL: 
fedora-websites 
Fedora Website Team's Trac instance
--
websites mailing list
websites@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/websites@lists.fedoraproject.org

Re: [fedora-websites] #369: Fedora Server: do not advertise 32-bit x86 media

[fedora-websites]

#369: Fedora Server: do not advertise 32-bit x86 media
-+
 Reporter:  sgallagh |   Owner:  webmaster
 Type:  enhancement  |  Status:  closed
 Priority:  major|   Milestone:  Fedora 24
Component:  getfedora|  Resolution:  fixed
 Keywords:  easyfix  |  Blocked By:
 Blocking:  391  |
-+
Changes (by robyduck):

 * status:  new => closed
 * resolution:   => fixed


-- 
Ticket URL: 
fedora-websites 
Fedora Website Team's Trac instance
--
websites mailing list
websites@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/websites@lists.fedoraproject.org