The i7/archive Github repo was an archive of inform7.com/write/extensions/ Nothing more, nothing less.
Very few people have used the IF Archive for individual extensions - it’s not really an ideal place for them.
Could you give me access to push to the repo? My username on github is, um, “neroden”, same as here.
I’ll start throwing up my half-finished extensions if that’s OK.
(P.S. The principle behind git, which is rarely explained, is that everything is a patch or a series of patches. Even adding the first file to the repository is treated as a patch on the “empty repository”. There’s then a “calculus of patches”. Obviously it doesn’t entirely store things that way under the hood but that’s the principle, and I’ve found if I think about it that way it all makes sense. Even the really irritating bogus merge conflicts.)
I have several patches for Undo Output Control by Erik Temple. I figured out a clean way to reduce the number of Inform 6 sections replaced while giving the game author more flexibility.
What’s the best way to suggest them to the current maintainer? Even if I get approved for github access, I certainly wouldn’t want to just push a change to anything outside my own folder without asking the maintainer.
Or should I just fork the extension? I guess that’s why extensions all have author names, is to allow forks without namespace conflicts…
I already added you to the group.
Even though you can commit directly, you could also commit to a branch and then make a pull request for review. Then we can all see what we think and say whether it should be incorporated into the extension or whether it would be better to fork the extension.
And for the record, Erik has transferred the maintainership for all his old extensions to the community.
OK, thanks very much for giving me the preferred protocol! I’ll set up a branch and queue it as a series of patches (since it’s a number of small tweaks). The community can then decide which of the patches to incorporate. 
Oh-kay, I’m getting
“remote: Permission to i7/extensions.git denied to neroden.
fatal: unable to access ‘https://github.com/i7/extensions.git/’: The requested URL returned error: 403”
Not sure what’s going on, so I just cloned the repo on github and am working with my clone.
You have to accept the invitation first. It should be in your notifications, and probably also by email.
OK, thanks. It looks like the invitation didn’t show up at all on github notifications for some reason (!!!), which is what confused me. I also use a different email for github than I use for most things, so I didn’t immediately check there… yeah, anyway, sorted now. Thanks.
Warning for others, github notifications might not actually show invitations.
Whew. Pull request made. I think I’ve got the hang of the workflow now.
Hello. I have just created my first extension and was directed here when I asked about where to publish it. Could you please invite me? My username is Pinmat135, same as here. (Warning: I know next to nothing about GitHub and created an account today so that I could put my extension in here.)
1 Like
Done!
If you just use the web interface you can add your extension by clicking “Create new file” from the repository front page. You’ll then need to add the folder name and extension name. If you don’t get it right, don’t worry, we can fix it later.
2 Likes
Thanks! I’ll put it in there in a bit, after I finish the examples that I forgot to add originally.
1 Like
Hi! Could I get access? I’m brirush84. I plan on submitting my Clues and Conversation. Thanks for setting this up!
1 Like
It seems like people are turning to the Friend of I7 Github repo as an alternative to the public library, since the status of the public library is unclear. And I had thought of the Github repo as being more of a place for in-progress or experimental stuff.
So I’m wondering…if I’ve got something on the Github repo that I decided not to finish, or didn’t submit to the public library, or don’t recommend that people use for whatever reason, can I mark it as such, or remove it, or something?
Feel free to add a comment saying it’s not ready for general use. Or just don’t add documentation - that’s what I’ve done for my rough extensions…
You can always change the read me on it to express your intent. If you don’t want to delete the repository out right, you can archive it, which changes it to read only:
https://github.blog/2017-11-08-archiving-repositories/#:~:text=To%20archive%20a%20repository%2C%20go,open%20issues%20and%20pull%20requests.
Thanks!
1 Like
FYI I’ve merged the current content of the Public Library into GitHub, so there’s now only one place you need to go if you want All The Things. (Well, apart from a few other extensions posted elsewhere.)
6 Likes
That’s great news, thank you!
Just noting that we’ve added the CC BY license file to the repository. Almost all extensions were already surely intended to be published under the CC BY license, but if there is anyone who has put their extensions into the i7/extensions repository who doesn’t want them published under that license, please let us know now and we’ll remove them.