I'm part of a small team that collaborates on projects. There's up to 50 projects in the queue or in progress at a time, all projects are very similar to one another.
We basically need some kind of task management platform with the following features:
- tasks need to be grouped by project
- we need to be able to discuss tasks
- we need to be able to attach a few files (mostly screen shots) to discussions
That's it really, but everything I've looked at seems to be either a kanban board which just doesn't work for us, or a small part of a larger project management / collaboration ecosystem which is kind of overwhelming.
We're presently using Asana, but while it does what we need IMO it does it very poorly - better suited to teams working on fewer more variable projects.
Of course I'd prefer self hosted & open source but that's not critically important.
Any suggestions welcome!
This is happening all over reddit.
Mods are posting all over the place saying "I have to bend over for the admins because if I don't they'll find someone else who will".
You do you but honestly I find this a bit weird. As an unpaid volunteer you don't have to do anything. Just resign. Reddit's not about to die but it's best days are in the past. I wouldn't want to be a part of the future of reddit.
The biggest problem I see is fragmentation, people are creating the same community in different instaces, /c/Piracy for example.
I agree, to an extent. You're right in that if you were part of the vibrant community of /r/piracy then it's miserable to see it shatter here on lemmy. That said, this only applies if you're expecting lemmy to be a 1 for 1 reddit replacement. For this type of community to remain cohesive, /r/piracy would have had to spin up their own instance and in /r/piracy direct everyone to lemmy.piracyinstance.whatever.
You can't really "fix" this in a central way because even if you did, it would be trivial to create an instance that would allow duplicate community names. Also, I can see a lot of use cases for lemmy which do not intend to be federated.
That said, it's not necessarily as big a problem as it appears, if you just accept that this is how the fediverse works. There's no single source of control, so of course people can create 147 different /c/piracy communities if they wish to. Once you accept that, then it's not really that difficult to subscribe to all the /c/piracy communities you can find.
The problem itself could be diminished by a few new features which I feel certain will emerge in the future:
- linked communities, where one communities content is syndicated to another. So if you post in !selfhosted@lemmy.world then you also post in !selfhosted@lemmy.ml. This would work differently to cross-posting, all comments would be reflected on both instances.
- grouped communities, where you can subscribe to a group of /c/selfhosted communities with one click, so you see them all in your feed.
While I'm not interested in encouraging /r/selfhosted users to leave reddit, I thought it would be good to have some discussion around the possibilities for a selfhosted community on lemmy.
It looks as though most users are washing up in !selfhosted@lemmy.ml, but this is but a temporary refuge in these troubled times. The single mod is not responsive, lemmy.ml is already struggling with load, and the background lemmy.ml community may not be right for us. If we set up shop here we're just going to have to move, probably sooner rather than later.
So if we move, do we create our own instance or move to an existing one better aligned with our needs?
Given that there don't seem to be any instances which are really ideal, the remaining advantages to choosing an existing instance is simply that we rely on someone else's infrastructure (and the associated time, skill, and responsibility). This is a significant advantage which makes this option tough to pass up, but the equally significant disadvantage is that we don't get our own place. It's like renting a room in a frat house rather than building our own mansion.
The remaining option is to create our own instance. If we were to go this route, in my opinion it is critically important that the responsibility for this be shared amongst several people. This dramatically reduces the odds that someone loses interest, or lacks the resources to support the community long term. While I'm certain that everyone in this sub could spin up an instance, we all know that providing high availability to potentially thousands of users is not something to be undertaken on a whim. There's a significant risk to the community in allowing someone to take this on themselves.
I think fosstodon (mastodon) with several admins is a good model of how something like this can work. I also think it would be a good idea to broaden the subject to FOSS rather than merely self hosting.
So the questions are...
Do you think we should create & support a community on an existing instance, or create our own instance?
If an existing instance then which one?
If a new instance then how would you like to see it operated?
Hard disagree.
Getting over-run by blog spam is entirely foreseeable.
With a single dead mod it's entirely foreseeable that we would have to relocate at some point which could be devastating when trying to preserve whatevers left of the community.
Looking at the list of instances there doesn't seem to be any really perfect options.
Honestly I would be most comfortable with an instance administrated by several people. It just increases the odds that admins will know what they're doing and not lose interest.
This is as good a place as any to ask... where should we set up shop? This community's sole mod @Zoe8338@lemmy.ml doesn't seem to be active.
A number of different self-hosting related communities have popped up in the last few days. I'm concerned that without a single focal point we won't hit a critical mass.
Is this the best place for us though? @Zoe8338@lemmy.ml is the only mod and they don't seem to be active.
Not really. It's incredibly frustrating and I've def lost some faith in humanity.
I thought /r/selfhosted would be ready to jump but everyone is like "but there's no users on lemmy" and "you'll split the community" and "we're going to go dark for two days - that will teach them!"
Consequently there's been no support for any single refuge.
Additionally people have set up several communities here with similar names in the past but now mods aren't responding so it's all a bit of a mess.
I guess it depends on your definition of "self hosting" but I'm in the process of migrating a lot of my services to a remote vps on vultr. It doesn't make much sense to have a big, hot server running at home that needs capacity to cope with peaks but isn't used 99% of the time.
Sharing server resources with other virtual servers is the most significant least pain to benefit ratio action I can think of.
All that will really be left at home is a torrent client and gerbera (upnp) instance which can happily run on a NUC with an nvme. gerbera won't do any transcoding so the load is negligible.
The reluctance of redditors to move to lemmy always amazes me.
Not surprisingly, there's a lot of posts in a lot of subs about the recently announced changes. In every post the same pattern is repeated ad-nauseum:
- "i hate reddit, it sucks here, I've always wanted to leave, I'm never coming back once this happens"
- "maybe we should move the sub to lemmy so we won't have this problem in future?"
- "but what about all our data, the wiki & post history and such"
- "but there's no users on lemmy"
- "but that would split the community!"
This is the case even in the subs I would have thought would be really keen to jump ship, like /r/selfhosted
I think this type of approach is the right idea though, a better ecosystem can only be good.
Generate beautiful ASCII art diagrams. Diagon is a collection of interactive generators. Math formulas, sequences diagrams, graph, border, ... This is written in C++, available online with WebAssembly.
Overview of alternative open source front-ends for popular internet platforms (e.g. YouTube, Twitter, etc.) - GitHub - mendel5/alternative-front-ends: Overview of alternative open source front-ends...