From Fedora Project Wiki
m (formatting changes) |
(Web app questions) |
||
| Line 2: | Line 2: | ||
** [[User:Wwoods|wwoods]] ''"if you were optimistic you could think that the other ideas might lead to a rawhide which is mostly non-broken"'': Sure, if we were doing everything else right this wouldn't be necessary. But relying on that assumption is just a way to avoid solving the problem. And we've had the problem for the past 5 years. Nothing makes me think it's magically going to go away now. | ** [[User:Wwoods|wwoods]] ''"if you were optimistic you could think that the other ideas might lead to a rawhide which is mostly non-broken"'': Sure, if we were doing everything else right this wouldn't be necessary. But relying on that assumption is just a way to avoid solving the problem. And we've had the problem for the past 5 years. Nothing makes me think it's magically going to go away now. | ||
** [[User:Wwoods|wwoods]] ''"what's the chances of that getting done dailyish?"'': We won't know until we try. Even if it's only happening every three days, or weekly - it's still better than what we have now. | ** [[User:Wwoods|wwoods]] ''"what's the chances of that getting done dailyish?"'': We won't know until we try. Even if it's only happening every three days, or weekly - it's still better than what we have now. | ||
* Who is writing the web application? If hosting in Fedora Infrastructure, we'd love to have it be python/WSGI-based. | |||
** If a prebuilt solution, can it integrate with FAS? | |||
** If we wanted single sign on with other Fedora web apps (and the auth provider is compatible), we'd need to be under a common domain. For instance, https://admin.fedoraproject.org/israwhidebroken. We could redirect israwhidebroken.com to a set of pages that don't require authentication in the web app. | |||
Revision as of 21:02, 18 June 2009
- markmc Would be useful, but if you were optimistic you could think that the other ideas might lead to a rawhide which is mostly non-broken. The 'someone from QA should file a ticket with rel-eng to create a "known-good" symlink' part worries me a little ... what's the chances of that getting done dailyish?
- wwoods "if you were optimistic you could think that the other ideas might lead to a rawhide which is mostly non-broken": Sure, if we were doing everything else right this wouldn't be necessary. But relying on that assumption is just a way to avoid solving the problem. And we've had the problem for the past 5 years. Nothing makes me think it's magically going to go away now.
- wwoods "what's the chances of that getting done dailyish?": We won't know until we try. Even if it's only happening every three days, or weekly - it's still better than what we have now.
- Who is writing the web application? If hosting in Fedora Infrastructure, we'd love to have it be python/WSGI-based.
- If a prebuilt solution, can it integrate with FAS?
- If we wanted single sign on with other Fedora web apps (and the auth provider is compatible), we'd need to be under a common domain. For instance, https://admin.fedoraproject.org/israwhidebroken. We could redirect israwhidebroken.com to a set of pages that don't require authentication in the web app.