I've created a github org, https://github.com/hyperhype and moved all my hyper* repos there, and given out owner invites to @cel and [@mixmix](@ye+QM09iPcDJD6YvQYjoQc7sLF/IFhmNbEqgdzQo3lQ=.ed25...
I've created a github org, https://github.com/hyperhype and moved all my hyper* repos there, and given out owner invites to @cel and @mixmix
would you like to add this repo to that org?
included is a script for adding everyone as owners - https://github.com/hyperhype/hyperowners
hypercombo is not on github. would it be better to move the org and the modules onto ssb?
I'd love to use all git-ssb but currently the difficulty for me is it doesn't handle notifications quite as well, and for @mixmix i understand he feels the code review flow is not as good. I did this mainly for @mixmix because he is doing lots of stuff that requires changes to the hyper* widgets and I wanted to get out of his way, and he had previously explained that he felt git-ssb was a bit more difficult for him to use.
that makes sense. i've joined the org and added you guys as owners to the hypercombo npm package. i'm leaving out this repo from github, although if someone else wants to mirror and maintain it there, that is okay with me. i will try to use this as impetus to further develop the ssb issue notifications and improve the git-ssb ui
hey @cel so it's clear I'm totally committed to getting this community onto git-ssb - it's totally the future I am investing in.
I think there's some changes I need and I tried ot code in git-ssb-web but found it pretty hard to read + modify. My push in patchbay has been about preparing the ground for a second push into git-ssb in a way that's going to play well with other parts of the eco-system and hopefully be easier to mod + extend.
My specific need for collaborative dev (namely review) is comments + conversation that are inline / point to specific lines of code.
@dominic I've heard you express 'I need notifications' or similar about git before. I'd love you to explain your workflow so that we can be super clear about what it is you thirst for. (i.e. which notifications are you reading - are you going to an overview of notifications page, or reading you notifications of edits in your email. What do you do with them when you see them, how do you process them?)
@mixmix thanks, that's good to hear.
i am thinking now about how to make comments on code work.
i talked with @dominic a few calls ago about the notifications thing and i think i know how that could work, but i had trouble fully implementing it at the time. i might revisit this soon
As far as I can tell, the client I'm using -- %minbay -- already has a notifications system built into it.
I know it's tempting to overthink this, but the immediate idea I had was just to tag people I want to know about the merge request in the merge request.
Built with git-ssb-web