Re: F21 System Wide Change: Cockpit Management Console
- Original Message - On Mon, Apr 21, 2014 at 1:38 PM, Stephen Gallagher sgall...@redhat.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/15/2014 11:29 AM, Kevin Fenzi wrote: ...snip... Special Requests: Cockpit would like to request an additional 2-4 weeks on the Fedora 21 schedule to ensure completion of the core functionality. So, you want to push final release out to november? Or can you expand on what you mean by 'on the Fedora 21 schedule' ? When I spoke with the Cockpit developers, there was concern that they would not quite be feature-complete by the currently-targeted Alpha date. In order to have a little breathing room, it was decided that we should request additional time there. Perhaps we could shave a week off off each of the Beta and Final deadlines to accommodate an additional two weeks on Alpha? (Of course, that carries risks on test coverage as well...) The purpose of requesting the additional time was to alert FESCo that there is a risk of delaying the Alpha release for this Change (if approved) and communicating that up front. Instead of delaying the whole release even more ... would it make sense to simply ask for this feature to have an exception to let it land in beta instead of alpha? OTOH this would kind of limit testing time for it. I think this definitely better way - not being as strict regarding deadlines for Cockpit and get some test coverage during later Test Day. Cutting one week from Alpha/Beta cycle is doable but only when it's really, really needed. We did this voodoo magic a few times to avoid Christmas etc. and believe me - that note in the Task Juggler source for schedule - never, ever, do this - is just truth. It pains. So the question is - is this Change that Change, delaying the WHOLE Fedora 21 schedule so much desirable? But I still prefer being more flexible with deadlines + scope cutting. Jaroslav -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: F21 System Wide Change: Cockpit Management Console
On Tue, Apr 22, 2014 at 05:06:33AM -0400, Jaroslav Reznik wrote: Cutting one week from Alpha/Beta cycle is doable but only when it's really, really needed. We did this voodoo magic a few times to avoid Christmas etc. and believe me - that note in the Task Juggler source for schedule - never, ever, do this - is just truth. It pains. And in practice, it's probably a lie -- those cut weeks get added back as delays later, so it's really just shuffling numbers around for extra work and no benefit. -- Matthew Miller-- Fedora Project--mat...@fedoraproject.org Tepid change for the somewhat better! -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: F21 System Wide Change: Cockpit Management Console
Jaroslav Reznik (jrez...@redhat.com) said: I think this definitely better way - not being as strict regarding deadlines for Cockpit and get some test coverage during later Test Day. I'd be fine with a later deadline for Cockpit if needed, especially since (from the feature page description) it doesn't seem to have much of a knock-on effect on other components. I'm actually a little curious how this isn't a standalone addition, aside from just the 'installed by default in Fedora Server' angle. Bill -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: F21 System Wide Change: Cockpit Management Console
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/15/2014 11:29 AM, Kevin Fenzi wrote: ...snip... Special Requests: Cockpit would like to request an additional 2-4 weeks on the Fedora 21 schedule to ensure completion of the core functionality. So, you want to push final release out to november? Or can you expand on what you mean by 'on the Fedora 21 schedule' ? When I spoke with the Cockpit developers, there was concern that they would not quite be feature-complete by the currently-targeted Alpha date. In order to have a little breathing room, it was decided that we should request additional time there. Perhaps we could shave a week off off each of the Beta and Final deadlines to accommodate an additional two weeks on Alpha? (Of course, that carries risks on test coverage as well...) The purpose of requesting the additional time was to alert FESCo that there is a risk of delaying the Alpha release for this Change (if approved) and communicating that up front. -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlNVAz4ACgkQeiVVYja6o6OLQACfVTHRFptZy6J4ExYISTaUcOXS I/oAn1i/tXg7uZLOlFXl38exyBVE7maJ =lAGh -END PGP SIGNATURE- -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: F21 System Wide Change: Cockpit Management Console
On Mon, Apr 21, 2014 at 1:38 PM, Stephen Gallagher sgall...@redhat.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/15/2014 11:29 AM, Kevin Fenzi wrote: ...snip... Special Requests: Cockpit would like to request an additional 2-4 weeks on the Fedora 21 schedule to ensure completion of the core functionality. So, you want to push final release out to november? Or can you expand on what you mean by 'on the Fedora 21 schedule' ? When I spoke with the Cockpit developers, there was concern that they would not quite be feature-complete by the currently-targeted Alpha date. In order to have a little breathing room, it was decided that we should request additional time there. Perhaps we could shave a week off off each of the Beta and Final deadlines to accommodate an additional two weeks on Alpha? (Of course, that carries risks on test coverage as well...) The purpose of requesting the additional time was to alert FESCo that there is a risk of delaying the Alpha release for this Change (if approved) and communicating that up front. Instead of delaying the whole release even more ... would it make sense to simply ask for this feature to have an exception to let it land in beta instead of alpha? OTOH this would kind of limit testing time for it. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: F21 System Wide Change: Cockpit Management Console
...snip... Special Requests: Cockpit would like to request an additional 2-4 weeks on the Fedora 21 schedule to ensure completion of the core functionality. So, you want to push final release out to november? Or can you expand on what you mean by 'on the Fedora 21 schedule' ? kevin signature.asc Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: JavaScript bundling (was Re: F21 System Wide Change: Cockpit Management Console)
On Fri, Apr 11, 2014 at 8:19 AM, Peter MacKinnon pmack...@redhat.com wrote: Is there circumstances whereby new reviews can be approved without FPC exception if those assets have not yet been packaged under the new web asset packaging guidelines and layout? There's currently a blanket exception for jQuery: https://fedorahosted.org/fpc/ticket/408#comment:9 To my knowledge, there is no such exception for any other libraries. Feel free to request one though; FPC will likely approve and I'll add my support just as I did with jQuery. :-) -T.C. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
F21 System Wide Change: Cockpit Management Console
= Proposed System Wide Change: Cockpit Management Console = https://fedoraproject.org/wiki/Changes/CockpitManagementConsole Change owner(s): Stephen Gallagher sgall...@fedoraproject.org, Marius Vollmer, Stef Walter The Fedora Server Product will ship the Cockpit Project as available by default, providing an approachable tool for system management. == Detailed Description == Cockpit is a server manager that makes it easy to administer your GNU/Linux servers via a web browser. * Easy to use Cockpit is perfect for new sysadmins, allowing them to easily perform simple tasks such as storage administration, inspecting journals and starting and stopping services. * No interference Jumping between the terminal and the web tool is no problem. A service started via Cockpit can be stopped via the terminal. Likewise, if an error occurs in the terminal, it can be seen in the Cockpit journal interface. * Multi-server You can monitor and administer several servers at the same time. == Scope == Inclusion of Cockpit as part of the default (not necessarily minimal) install set for Fedora Server * Proposal owners: ** Support for a modular architecture ** Improved network management * Other developers: N/A * Release engineering: Inclusion of cockpit into comps.xml * Policies and guidelines: N/A Special Requests: Cockpit would like to request an additional 2-4 weeks on the Fedora 21 schedule to ensure completion of the core functionality. ___ devel-announce mailing list devel-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
JavaScript bundling (was Re: F21 System Wide Change: Cockpit Management Console)
Asking for a friend... Trying to get clarification of the current JavaScript guidelines (https://fedoraproject.org/wiki/Packaging:JavaScript) since it is potentially impactful for a web UI review request (https://bugzilla.redhat.com/show_bug.cgi?id=1076506) I'm working on. Cockpit and some other recent reviews appear to bundle JavaScript libs from other projects; in this particular case bootstrap, jquery, and term. My understanding is that the JS guidelines (AFAIK ratified last August) are now in force and that any such bundling requires FPC exceptions (temporary or otherwise). My working assumptions on assessing if prohibited bundling is occurring: * minification has no impact * locating bundled JS assets in a separate no-arch sub-package also has no impact Is there circumstances whereby new reviews can be approved without FPC exception if those assets have not yet been packaged under the new web asset packaging guidelines and layout? Any specific guidance would be much appreciated. Thanks! \Pete On 04/11/2014 09:41 AM, Jaroslav Reznik wrote: = Proposed System Wide Change: Cockpit Management Console = https://fedoraproject.org/wiki/Changes/CockpitManagementConsole Change owner(s): Stephen Gallagher sgall...@fedoraproject.org, Marius Vollmer, Stef Walter The Fedora Server Product will ship the Cockpit Project as available by default, providing an approachable tool for system management. == Detailed Description == Cockpit is a server manager that makes it easy to administer your GNU/Linux servers via a web browser. * Easy to use Cockpit is perfect for new sysadmins, allowing them to easily perform simple tasks such as storage administration, inspecting journals and starting and stopping services. * No interference Jumping between the terminal and the web tool is no problem. A service started via Cockpit can be stopped via the terminal. Likewise, if an error occurs in the terminal, it can be seen in the Cockpit journal interface. * Multi-server You can monitor and administer several servers at the same time. == Scope == Inclusion of Cockpit as part of the default (not necessarily minimal) install set for Fedora Server * Proposal owners: ** Support for a modular architecture ** Improved network management * Other developers: N/A * Release engineering: Inclusion of cockpit into comps.xml * Policies and guidelines: N/A Special Requests: Cockpit would like to request an additional 2-4 weeks on the Fedora 21 schedule to ensure completion of the core functionality. ___ devel-announce mailing list devel-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce -- Peter MacKinnon MRG Grid/Big Data Red Hat Inc. Raleigh, NC -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
