[fedora-websites] #367: website and login problems and confusions
by fedora-badges
#367: website and login problems and confusions
----------------------+------------------------------------
Reporter: oskar | Owner: webmaster
Type: defect | Status: new
Priority: major | Milestone:
Component: General | Keywords: link, mailing list, ux
Blocked By: | Blocking:
----------------------+------------------------------------
Each and every website connected to fdora project uses different
terminology furthermore different authentication system. I.e. I wanted to
join to the design team at the link
https://fedoraproject.org/wiki/Join_the_Design_Team
As suggested I had to subscribed to the mailing list, however when i
registered it turned out that the link at the above page points to some
old version of the mailman system where I had to create a subscription. So
it didn't work. Then I found out the sudden blue a different link where I
could register with mozilla persona login that is third one given the fact
that I had to create a fedora account as well as suggested on the join
page.
I also checked and in the websites group page at the join to mailing list
section the link is wrong as well. here
https://fedoraproject.org/wiki/Websites/Join
So my original plan was to join to the design team, however now i have to
keep in mind 4 different login credentials, and at each page there is a
different naming structure. E.g. to submit this bug report i was asked for
an open id which turned out to be equivalent with my fedora account, but
with FAS account cannot access the same subscription I did with persona
at the mailing list.
My brief suggestion was to try to consolidate all these websites and
services and use a single type of authentication service, that is call the
same at each and every websites.
Eg. now i have different credentials for fedora account, to the wiki site,
to the mailing list where my suggestion was to use only the
fedora account that was valid to everywhere.
thanks,
Karoly
--
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/367>
fedora-websites <https://fedoraproject.org/wiki/Websites>
Fedora Website Team's Trac instance
8 years
[fedora-websites] #375: Write websites docs for pagure
by fedora-badges
#375: Write websites docs for pagure
-----------------------+-----------------------
Reporter: robyduck | Owner: webmaster
Type: task | Status: new
Priority: major | Milestone: Fedora 24
Component: General | Keywords:
Blocked By: | Blocking:
-----------------------+-----------------------
As for ticket #374 we could move all our docs to pagure, as there is a
nice feature built in pagure. For now I moved there just the release SOP,
but we could, as we do not have many wiki pages, move it all to pagure.
To make this and get a nice layout, we should use sphinx, which is
automatically rendered by pagure, it permits to make an index and can
include all kind of documentation we are using actually.
The real pro here is to have all websites resources in one place :)
If anyone wants to work on this, please ping me to coordinate the work and
to get write access.
--
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/375>
fedora-websites <https://fedoraproject.org/wiki/Websites>
Fedora Website Team's Trac instance
8 years
[fedora-websites] #380: Prepare websites for F24 Alpha release
by fedora-badges
#380: Prepare websites for F24 Alpha release
-----------------------+-----------------------
Reporter: robyduck | Owner: webmaster
Type: defect | Status: new
Priority: major | Milestone:
Component: General | Keywords:
Blocked By: | Blocking:
-----------------------+-----------------------
Yes, it's that period of the year again, F24 has been branched and a new
release cycle has started. We have some new stuff to do and are on a new
repository, so let's start a bit earlier:
'''IMPORTANT NOTE:''' The web repository is now on pagure and we won't
have anything of the F24 release cycle on our old fedorahosted.org repo.
Please reclone the new repo and push your work there: https://pagure.io
/fedora-websites
On the new repository the branch f24-alpha has already been created and
the globalvars updated to the Alpha release. From now on you can easily
follow our release updating process (probably it still needs some fixes)
on the pagure documentation:
https://docs.pagure.org/fedora-websites/websites_release.html#update-
website-for-alpha-release
Also:
* Create a page for the new Astronomy Spin - ticket #371
* Fedora server: no 32 bit images anymore on the websites - ticket #369
* If possible, let's show the Atomic ISO installer more prominent - ticket
#366
* We need to check if the Atomic and AMI script work for prerelease
images, and if not fix them.
* We never built anything from the pagure repo. Setup the Infra part ASAP
for staging to see what happens.
Prerelease images are unstable, so we can probably look for a place where
to mention also rawhide, which also is rather unstable. We have ticket
#373 requesting it.
Let's add anything else to this ticket, thank you.
--
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/380>
fedora-websites <https://fedoraproject.org/wiki/Websites>
Fedora Website Team's Trac instance
8 years
New websites repository created on pagure: RECLONE PLEASE!
by Robert Mayr
Hi,
after some tests and discussions about the best way of creating our new
websites repository on pagure, I've just created a new project:
https://pagure.io/fedora-websites
The repository went down from uncompressed 890MB to 180MB as desired and
cloning it should be pretty fast now;
IMPORTANT: ALL GITFEDORA-WEB MEMBERS NEED TO RECLONE THE REPO!!!
git clone ssh://git@pagure.io/fedora-websites.git
If you never logged in to pagure, please do so and let me know, in order to
add you to the group with commit access to the repository. Actually we have
two branches, master and f24-alpha.
In the next days I'll add the source files of the documentation I wrote so
far, so anyone can also contribute there.
The workflow for the next weeks is a bit awful, but it will not last too
much. Websites are still build from the fedora-web repository on
fedorahosted, but we will test the build from pagure with the staging
websites, as soon as we have something new in that branch.
For any changes on the master branch we need to sync them out manually, so
please push to fedora-web, but do your fixes also in fedora-websites on
pagure (I have choosen a different name because it's better to not mix the
two repos up, they are very different actually).
To avoid this double coding we should try to not push anything to
production right now, unless it is "very" important. If we can wait with
the changes until F24 Alpha, let's do so.
Please ping me or drop me a message if you have any doubts or questions, I
will try to update this post anytime something is changing in our workflow.
We will also need to update the wiki...
Thanks.
Kind regards.
--
Robert Mayr
(robyduck)
8 years, 1 month
Move web repo to pagure - considerations
by Robert Mayr
Hi all,
in the last weeks we had some discussions on IRC about moving the
webrepository from fedorahosted to pagure and I also filed a ticket [1] to
collect opinions about this proposal. There are several advantages for us
to move over there and we will start moving with the next release cycle,
which has started these days (we will branch during weekend or next week
probably).
I've set up a testing repository [2] where I also wrote some docs to test
how this would look like. It is working really fine and having a unique
place for all our stuff where we can easily handle PRs is a big enhancement.
At this point there are several opinions about how to move to pagure.
Personally I want to reduce the weight of the web-repo, which is about
660MB or better, 870Mb uncompressed. Not only we have many branches in
there, the reason of all these MBs are static binaries and mainly images we
collected over all the last years.
If we want to solve this problem, we have two options, in both cases all
team members MUST rebase or even reclone the repository:
1) We can run a "git gc --aggressive" on the repo, but a test (thanks nb)
confirmed we would not save too much space. Pros for this solution are:
* people can just rebase and setup the new pagure URL in the git config file
* we keep all history and commit credits
* we can keep also branches where we have ongoing development
2) We could start a complete new repository, which would give us also the
possibility to delete many heavy binaries we are not using at all. We would
probably end up with an uncompressed size of less than 200MB. There are
several cons, but in this specific moment we are able to handle them:
* we will loose commit credits and history ^
* we cannot build any other branch than master and f24-alpha ^^
* all members MUST reclone the repository (has the advantage that it would
be a clean solution and it will be much faster than now)
^ fedorahosted.org would be still there and if needed we can look in the
web UI if we need to find out how things changed in a specific commit.
Also, people can obviously keep the old fedora-web repo locally and use it
for investigations. Commit credits could be saved in a CREDITS file we can
put into the new repo.
^^ Actually all websites are built against master branch and we would build
staging with f24-alpha. Our devel branches are just 2, both of them can be
merged to master without creating conflicts or risks to break our
production websites.
All this said, personally I'd really like to go for a new repository and
archive all the stuff we have now in the old fedorahosted.org repo. Any
opinions about that? Other ideas or concerns?
Thank you, specially for reading my long mail until the end.
[1] https://fedorahosted.org/fedora-websites/ticket/374
[2] https://stg.pagure.io/Fedora_Websites_test
--
Robert Mayr
(robyduck)
8 years, 1 month
[fedora-websites] #374: PROPOSAL: move websites repository to pagure
by fedora-badges
#374: PROPOSAL: move websites repository to pagure
--------------------------+-----------------------
Reporter: robyduck | Owner: webmaster
Type: enhancement | Status: new
Priority: major | Milestone: Fedora 24
Component: General | Keywords:
Blocked By: | Blocking:
--------------------------+-----------------------
Infra team and many other projects are moving slowly to pagure and I'd
like to see also websites stuff moving there. Pagure has improved a lot
recently and actually offers the same (if not even more) functions as
fedorahosted. Other features:
* pagure supports pull requests, so any contributor can submit fixes, even
if he is not in the websites team
* pagure also supports filing issues (like github), would be great to have
a unique place where to handle the repo '''and''' the trac.
* pagure also has a docs section, we can put our SOPs there and also other
documentation
Obviously all the other functions are also there, tagging, webhooks and
and and...
I've put a testing repo in https://stg.pagure.io/Fedora_Websites_test if
you want to take a look (tell me if you want to be added as committer).
[[br]]
Docs for pagure is available here: https://pagure.io/docs/pagure/
My idea would be to start using the pagure repo for the upcoming F24
release cycle, so code and build staging websites there and then move over
all the production websites once we release F24 final. That way we will
have time to test issues and see how to handle the repo on pagure.
Thoughts? Other ideas? Suggestions?
--
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/374>
fedora-websites <https://fedoraproject.org/wiki/Websites>
Fedora Website Team's Trac instance
8 years, 1 month