Add note about where to find up to date info #26
Conversation
* changed terms in how to join the workgroup. * addressed @bill-auger concern.
readme: proofread
* remove "W3C" from the license addressing document.
cblgh
changed the title
|
the forum information needs updating actually - the socialhub forum has not worked out as well as we had expected - as of last week, there is a new forum on the FeNeAs website; which has a primary category for ForgeFed discussions https://talk.feneas.org/c/forgefed there is sufficient reason to believe that it will be better-maintained and reliable going forward; and that it would be best to start using that one before there become too many links pointing to the socialhub forum - we expect that the FeNeAs will be the stable community forum into the future i have updated the pinned issue #24 with the new information - the entire "ForgeFed Community Forum" section should be changed in this PR |
|
i should add also that there is an updated README on the notabug repo https://notabug.org/peers/forgefed you could simply take that README verbatim; because ideally this and the notabug repo should be mirrors of each other - if i had write access to this repo, i would have already cloned the entire notabug repo to this repo and they would be in sync now; but AFAIK, there is only one person with write access to this repo, and it is not clear that he intends to actively maintain it |
|
i suppose i should have tried this sooner; but i was able to mirror the notabug repo as a second repo to this 'forgefed' organization https://github.com/forgefed/forge-fed still less than ideal though, as the previous discussions and external links point to this repo; but i will try to keep that second one in sync for the time being |
|
@bill-auger ah that's definitely a start! 🎉 i'll leave this open in case the person with write access wakes up from their slumber and decides to perform one last action as maintainer :~ |
|
@bill-auger might be worth the effort to write in the description field github has that it's a mirror, and link to the notabug repo in the website field |
|
its not possible - the only thing that anyone else can do on this repo is to moderate the bug tracker - but no work was ever added to this repo, so there will be no bugs filed - and there is a proper discussions forum now; so there is not much to do on this repo at all, unless koala wants to revive it someday |
|
@bill-auger ah sorry, i meant on your newly created repo. surely it should be possible to direct folx to the notabug repository both in the description and website fields there ^_^ |
|
looks like this has since moved also?
https://socialhub.network/t/moving-to-talk-feneas-org/629
…On Fri, Jul 5, 2019, 3:46 AM Alexander Cobleigh ***@***.***> wrote:
I came across this repository in search of federated pull request for
gitea (go-gitea/gitea#184 <go-gitea/gitea#184>),
and at the outset this project as a whole seems to be dead.
But it isn't! 🌱
I've updated the readme with @bill-auger <https://github.com/bill-auger>'s
response from #24 (comment)
<#24 (comment)>
cc @yookoala <https://github.com/yookoala> @Arkanosis
<https://github.com/Arkanosis>
------------------------------
You can view, comment on, or merge this pull request online at:
#26
Commit Summary
- add note about where to find up to date info
File Changes
- *M* README.md
<https://github.com/forgefed/forgefed/pull/26/files#diff-0> (19)
Patch Links:
- https://github.com/forgefed/forgefed/pull/26.patch
- https://github.com/forgefed/forgefed/pull/26.diff
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#26?email_source=notifications&email_token=AABZCVZC76ZWHCE26YDGL4LP54KAJA5CNFSM4H6JW35KYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4G5QTATA>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABZCV35URDPO44M2UGJXPLP54KAJANCNFSM4H6JW35A>
.
|
|
techknowlogick -
that one change is not enough - the preceding paragraph also mentions socialhub as the forum host
i have updated the pinned issue #24 with the new information - the entire "ForgeFed Community Forum" section should be changed in this PR
but ideally, if anyone can modify the repo, the best thing to do would be to wipe this repo entirely and replace it with the mirrored repo https://github.com/forgefed/forge-fed/ - that already includes the most complete and up-to-date documentation
|
|
@bill-auger not sure if by "wipe" you mean delete or overwrite, but this repo has quite a few stars & watchers which could help with getting more people onboard. |
|
just a confusion of terminology - "this" thing that has "stars"
and "watchers" is not a "repo" - it is a forge website (a
project management tool), which is used by some, but not all,
contributors to the over-all forge-fed project - there is much
more to a forge than a VCS repo - a forge may include a git
repo, but also several other optional things that are orthogonal
to version control, such as a wiki, an issue tracker, mailing
lists, forums, and other bells and whistles
the actual "repo" containing contributions to the forge-fed
project is currently mirrored on three different forges: github,
pagure, and notabug (and on several of the contributors local
machines) - currently, the only project management tool that can
be easily shared across different forges is the VCS repo - that
is the one core feature of forge that forge-fed does not need to
handle; because the repos are already standardized - the goal of
forge-fed is to make those other forge features as general as
the VCS repos already are - even more-so general actually;
because one of the features is to abstract away the peculiarities
of the different underlying version control and code review
workflows, including patches via email
so yea, i was not suggesting to destroy the entire github project -
it would be swell to keep all of the stars and what-nots; but again
that is entirely up to one person, who is apparently no longer
interested
|
|
What would it take to get said person to transfer ownership of the repo and/or org? |
|
there is no ownership of an organization - that is exactly
what distinguishes them from repos under per-user namespaces -
organization have a permissions system which determines which
people can perform certain actions, such as write access to
certain repos
what it would take, is about 20 seconds and 3 mouse clicks, if
that person wanted to do it - but AFAIK, he has not read or
interacted with this bug tracker or the repo in over a year
FWIW, the current repo is mirrored on several different servers
now, including another repo associated with this github
organization, and there is a proper web forum for discussions
now, and also a mastodon presence; so there is not such urgency
to maintain this repo as there was last year
|
|
Uggh, what happened to this repo now? Why was not this PR merged? Can anyone clean up the confusion. I just came in here thorough links (gitea) and only see troubles in this PR, but really don't want to read it all. Mark this as deprecated, if you have a new repo?? |
|
rugk -
please do read threads before posting - your questions have been
asked and answered already, on this same web page - you should
not expect anyone to answer them again only for your benefit -
that is a matter of common netiquette
|
|
This is a huge thread and I've asked for a small summary… Also there are multiple threads/issues in here already and this does not really help anyone, if one has to dig through a whole repo to find out what's up here… |
|
yes this repo fell into an unfortunate state of neglect - whatever link
that you followed on some other boards is simply outdated - no work
was ever actually done in this repo - people just need to update
their links to reflect the current state of things
that is why there is a single "pinned issue" #24 explaining the
current status - it is the most that can be done with this repo; but the
answers to your specific questions are all in this thread
|
AFAIK you just need to review it. But approving! Not only comment… |
|
@rugk I approved it, and it showed me a different message saying that only an admin can merge pull requests. |
|
|
Co-authored-by: techknowlogick <matti@mdranta.net>
I came across this repository in search of federated pull request for gitea (go-gitea/gitea#184), and at the outset this project as a whole seems to be dead.
But it isn't! 🌱
I've updated the readme with @bill-auger's response from #24 (comment)
cc @yookoala @Arkanosis