Skip to content
This repository has been archived by the owner on Oct 29, 2018. It is now read-only.

Archiving project #628

Open
raelgc opened this issue Oct 25, 2018 · 5 comments
Open

Archiving project #628

raelgc opened this issue Oct 25, 2018 · 5 comments

Comments

@raelgc
Copy link
Owner

raelgc commented Oct 25, 2018

In the beginning I've created this project because Slack had no client for Linux. Later, people asked to keep alive due better integration with Unity, better memory usage and due open source nature.

But now:

  • Slack official Linux client is a first citizen (receiving all features as OSX and Windows)
  • The HTML engine used by Scudcloud (webkit) is in a semi-abandoned state: new versions are not even compatible with the new JS used by Slack (to keep ScudCloud working, we should use another engine)
  • Slack has no official API: every JS code I've wrote in the past was using reverse engineering, which requires a lot of time
  • Slack keep moving fast: they keep adding and changing JS internal code really fast, which requires often updates in ScudCloud code to keep it compatible
  • Slack official client has improved memory management: now they move not often used teams to a "hibernated" state (that will be notified from new messages)
  • I've always been the only developer for ScudCloud, but receive some contributions (in form of pull requests) before Slack released their official client. After its release, people lost motivation to send contributions.

So, if someone has any thoughts, I'm really open to ideas.

@stieg
Copy link
Collaborator

stieg commented Oct 25, 2018

Hey @raelgc ,

You have been fighting an uphill unending battle as a one man army for sometime and that is a praiseworthy task on its own. Maintaining a project across multiple Linux distros on its own is challenging enough. Yet you have done this and also had to reverse engineer their work to get Scudcloud to function: a major pain in the butt and (I would argue) the primary reason of this issue here (though the state of the HTML engine is also not good either).

Honestly you have to look within yourself and ask what you want from this project. What drives you to come back and maintain this project day after day and is that what you wish to be doing? I believe this is where your answer lies.

There are some benefits to ScudCloud in its current form (as mentioned above) but without some stability backing your work (like a published API upon which your work can be built, other developers being able to contribute, etc) this project is just going to continue on its current path. From my perspective (and limited contributions to the project) some major change is needed to keep this going; otherwise retirement may be the only other option if you don't care to maintain it further (implied from your initial comment, but not explicitly spoken).

EDIT: Spelling and punctuation.

@ainola
Copy link

ainola commented Oct 28, 2018

Thanks for all of your hard work. Your talents are best put elsewhere when Slack has no desire to make it accessible (and acts aggressively to those that dare to impede on their holy brand).

I'll make a note on the AUR package to try and stave off bug reports.

@SolarAquarion
Copy link

I have requested a deletion of the package

@stieg
Copy link
Collaborator

stieg commented Oct 29, 2018

Filed https://bugzilla.redhat.com/show_bug.cgi?id=1643821 on RHBZ to retire Scudcloud there.

@raelgc
Copy link
Owner Author

raelgc commented Oct 29, 2018

Thank you, guys. I'll edit the README to make clear the project is archived.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants