Pull requests and issues closed by the bot

[shadoWalker89]

Hi guys,

So i have pull requests that were closed by the github bot and or will be closed due to the fact that they didn't receive any answer from the maintainers of the repo.
I see that my pull requests and many others are fairly simple and clear, but they stay unprocessed.
That will add up to the long queue of pull requests, why not make a decision and choose to merge them or close them ?

[prudho]

Well, the main issue is that @jlukic seem no longer interested in maintaining this repo anymore, and no one but him can merge pull requests. Maybe @hammy2899 has some powers to move things... or this project is doomed to die or be forked... #6109 must be reopen...

[y0hami]

Ok so I see a lot of people have been questioning the state of development for SUI over the past month and believe it or not so have I, I haven't had a response from Jack for about 2 months now and the last time I heard he was quite busy with work (work-related trips etc.). I do see a lot of people care about the project and want to help out.

I have also been quite busy the past month with work but have tried to jump on Github at least once a day to sort through issues and I am hoping I can continue this but I do understand it's not enough since there is no real way to get changes merged.

My plan is, if enough people want to collaborate and form a team for a community fork I will do that this week and will start merging changes for bugs and features. Keep in mind I will be forking with the intent to merge back into this repo if Jack does agree to start active development again. That being said I will keep the fork in the same mindset as Jack for changes etc.

[brody2consult]

I would rather see some more discussion before such a fork. I did not think @jlukic was the only owner. I would vote for more noise and discussion on GitHub and other places such as Twitter and private email until we can get to the bottom of this.

[prudho]

@brodybits there's a gitter here where we can talk about it.

That being said, SUI need to move further, even without @jlukic. This is not the first warning about the lack of maintenance on SUI (see #6109, #4886, #4059 and #3637).

[shadoWalker89]

Can't jack just give you @hammy2899 admin rights on the repo ? Or maybe transfer it to you if he cannot maintain it.

Let me put this way :

• I have never enjoyed working with a css framework like i do with semantic.
• When i worked with bootstrap i always need to install plugins for doing various things, i rarely do with semantic.
• Semantic should not depend on one person, there should be a team, see https://github.com/laravel/framework/ there is a community team helping taylor, sorting issues and pull requests for him and that way cut down the number of irrelevant issues and pull requests ...
  i understand that is hard and overwhelming to maintain something as big as semantic, that is why @jlukic should let in more people to help him or pass down the torch if he is no longer interested.

I wish that i had more experience on the inner things of semantic so i can help internally as a member on the repo.
But i can help as a user of semantic by replying to issues and try to help people.
I think there is a lot of people willing to to the same if the project is still active and not dead.
I really do not want semantic to die, it is such a amazing framework.

[GammaGames]

This subject has been discussed in 6109, and it sounded like he wanted a system to code review contributors for pull requests, but I'm not sure much work has gone into that. Last time this came up we decided to wait until Jack replied (which he did, and it was a good answer that addressed the worries in the issue).

Keep in mind I will be forking with the intent to merge back into this repo if Jack does agree to start active development again.

It just seems like, until Jack can come back with a more reliable schedule or a team is added, forking with the intent to merge back is a valid and positive direction. And I would love if the other branch had a tag that prevented the bot from closing issues with a certain tag. The bot is helpful for closing issues that don't need to be open, but closing issues or prs without any feedback from devs can be irritating.

[arjarn]

In my mind, fork is needed. I'm agree with @hammy2899 dev team should keep mind of SUI. In first, perhaps only bugs fix and if good synergy perhaps extend it ;)

[brody2consult]

In terms of forking @morganbarrett already made a fork in https://github.com/morganbarrett/Vanilla-Semantic-UI that replaces jQuery dependency with a Vanilla JS solution. Maybe a good starting point?

[y0hami]

@brodybits Since the intent will be to merge back I don't think we should use Vanilla SUI + Jack has commented about removing jQuery multiple times. #1175 (comment) #1175 (comment) #1175 (comment)

[prudho]

People interested in a fork should join us here to talk about.

[douglasg14b]

@prudho
The problem with referring to gitter chat or discord is that many can't join in on the discussion, as it happens in spurts, and in-the-moment. The only way a discussion can be held asynchronously from interested parties in many different timezones is somewhere more static, like here. Otherwise you get a small subsection of the community that is online at the time.

[prudho]

@douglasg14b You can also joining us here now.

[GammaGames]

Jack has commented on the matter as well, so it looks like progress will be on pause for a bit anyway: #6418