Notices tagged with gitlab, page 4

@adfeno also, why start a new repo-hosting packages when there are already multiple free code options; #GitLab, #Gogs, #Gittea, #Phabricator, and whatever #Savannah runs on? #WhyReinventTheWheel
@teslas_moustache

@teslas_moustache have you looked into #ForgeFed? That's exactly what they are working on, but in the form of a set of AP extensions that existing packages like #GitLab, #Phabricator etc could implement, so their instances can all become part of a single federated GH replacement.
https://github.com/forgefed/forgefed@adfeno@ecodigital.social

@sir @Wolf480pl @Michcioperz in case the context wasn't clear, I was picking up on our previous conversation about whether it is useful to engineers to have drive-by contributions, particularly from non-engineers. Engineers and designers developing user-facing software can be aided greatly by having end users file bug reports, and communicate their feature and UI needs. Web-based tools like GH and #GitLab were created to serve those needs. This, specifically, is what needs federating.

Big ups to @lightone who set up this guide, and is the lead maintainer. I'm doing my best to help by maintaining watchlists on an internal wiki (on #GitLab) to inform the ongoing development of the guide, reporting bugs, and so on. Volunteers welcome, to help with;
a) gathering and analyzing info about new developments in fediverse software
b) writing content to help new users understand the fediverse better
c) keeping all the info on the production site up-to-date.

Great stuff @lightweight ! What's the URL of your #GitLab instance? I'd add it to the list I've been aggregating here:
https://wiki.p2pfoundation.net/List_of_Community-Hosted_GitLab_Instances

@joshsharp OK, so technical users are even harder to lock-in because they know what else they can use, and how. If they don't care about software being proprietary, why use #ChangeMap.co instead of GH or BitBucket? If they *do* care about software freedom, why use it instead of #GitLab (Expat license) or #Phabricator (Apache 2.0)? If ChangMap is #FreeCode, you offer something GH etc don't, and you're being evaluated alonside GL or Phab on features, not software freedom.

#gitlab

Gitlab quick actions is a really nice shortcut
https://docs.gitlab.com/ee/user/project/quick_actions.html

Quck actions in gitlab work by typing commands as comments

i.e Commenting
/unlabel ~Doing
/label ~Production

Removes label "Doing" and adds label "Production"

I wish there would be a way to create a conditional statement to apply these rules for issues i.e. remove 'Doing' label when issue is closed. Add 'Production' label when appropriate CI pipeline finishes.

Anybody know how to install/use #Pandoc alongside #Jekyll on #gitlab CI?

I have everything working except the ability to use Pandoc.

https://gitlab.com/devinberg/jekyll-scholar-site/-/jobs/97129275

What stupid mistake am I making that the one blog post on this site results in a 404?

https://devinberg.gitlab.io/jekyll-scholar-site/

Source: https://gitlab.com/devinberg/jekyll-scholar-site

#gitlab #staticsitegenerators #jekyll

Is there a list of public #gitea / #gitlab / #gogs instances somewhere?

I've tried searching around a bunch but haven't come up with much.

Ouh, le vilain message d'erreur #Gitlab « This project was scheduled for deletion, but failed with the following message: PG::QueryCanceled: ERROR: canceling statement due to statement timeout CONTEXT: SQL statement "DELETE FROM ONLY "public"."ci_build_trace_sections" WHERE $1 OPERATOR(pg_catalog.=) "section_name_id"" : DELETE FROM "projects" WHERE "projects"."id" = [...] » #SQL

Love watching the post-mortems of #gitlab switching providers.

Really shows the challenges of cloud-hopping, and how even though APIs are similar, the infrastructure is different.

I remember they had to hack around IO issues moving to Azure, and now on GCP they need to run 4x more git workers because bcrypt functions run more efficiently on Azure compared to GCP for some? reason?

Any masto folks running a #gitea / #gogs / #gitlab server with open registration? (not specifically for mastodon dev.)

if not, any interest in doing a shared one?

"NOTE to users in Crimea, Cuba, Iran, North Korea, Sudan, and Syria: GitLab.com may not be accessible after the migration to #Google" - Really #Gitlab, you are moving to a platform which will cut off access for people in all this countries? https://about.gitlab.com/2018/07/19/gcp-move-update/

Socialhome 0.9.0 released

Long overdue, this release brings a few long awaited features and privacy related improvements. A total of 105 commits went into this release by two authors, changing 175 files (4476 insertions, 1958 deletions).

This release makes #Socialhome and #GDPR friends. Users can now delete and export their data, and admins can publish terms and privacy documents.

Other main features include support for limited content, notifications on mentions, admin improvements, tag search and the new local content stream. See below highlights for more details.

Highlights

• Limited content is now supported 🙈 💪

Limited content can now be created using the web create form. Note, API does not currently allow creating limited content (except replies to limited content). Once create form is ported to the API, things should be refactored there, right now had no bandwidth to ensure both work.

Limited content is shown in the stream with a lock symbol. The create shows some extra fields for limited content. These include “recipients” and “include following”. Recipients is a comma separated list of target profile handles the limited content will be sent to. Include following will populate recipients (on save) with all the profiles that one follows. Later on we will add contact lists for better targeting.

Limited content visibilities can be edited. If someone is removed from the target recipients, a retraction will be sent to try and delete the content remotely from the target recipient.

Currently recipients must already be known to the server, in the future a remote search will be done if the profile is not known. Any known remote profile can be targeted - it is up to the receiving server to decide whether to accept it or not. For local profiles, those of visibility SELF (ie hidden) cannot be targeted.

There is also a new stream “Limited” available. It shows all limited content visible to you.

• Add “Local” stream which contains only content from users registered on the same server.

• Mentions are now parsed out of incoming remote content and locally created content.

Currently the only syntax supported is the #Diaspora mentions syntax, ie @Name. Currently Socialhome users can create mentions by using the syntax manually. UI layer will be added later to choose people using the standard @ syntax to trigger search.

• Searching for hashtags is now possible using the global search

• Admins can now add Terms of Service and Privacy Policy documents to the site. Default templates are provided in the admin. These can be published as is or modified to suit the site.

• Users can export their data from the account settings. In addition to user and profile data, this export contains a list of profiles followed, content (including shares and replies) and a zip file of image uploads. An email notification will be sent to the user once the export is ready for download from the account page.

• Add possibility to delete user account. Deletion is permanent and will delete all created content including uploaded images. Delete request for profile and related content will be sent to remote servers.

• Admin pages are now linked to from the new navbar cogs dropdown menu. New admin pages have been added for content and profiles.

• Many fixes to stabilize the resource usage of streams precaching.

See the full changelog here.

What's next?

Limited content initial support was one of the goals of this release, and that has now been done. One of the other most wished for features has been the possibility to follow tags. This will most likely be included very soon for the next release.

The one major feature that has been postponed for a long time is #ActivityPub support. To finally move this forward, it is likely that no other large features will be worked on for the next release other than following tags and adding ActivityPub support to the federation layer.

Source code hosting

This release will most likely be the last release done exclusively through #GitHub. Migration will soon happen to a #Gitlab instance. While development will happen through Gitlab, there will be mirroring to the current GitHub repository, so that contributing through that will also be possible.

What is Socialhome?

Socialhome is best described as a #federated personal profile with social networking functionality. Users can create rich content using #Markdown. All content can be pinned to the user profile and all content will federate to contacts in the federated social web. Currently federation happens using the Diaspora protocol. Federating using existing protocols means Socialhome users can interact with tens of thousands of other users.

Please check the official site for more information about features. Naturally, the official site is a Socialhome profile itself.

Official site: https://socialhome.network.

Contribute

Want to work on a #Django and #Vue.js powered social network server? Join in the fun! We have easy to follow development environment setup documentation and a friendly chat room for questions.

• Documentation
• Chat room info

#changelog #news #socialnetwork #thefederation #selfhosting

@strypey
>ok, so why us #Taiga instead of just using #Gitlab?

it was related to part of the conv. where it was about that 'maybe not using this because it is missing that'.

I just wanted to bring up the point that if there are multible jobs need to be done, it's ok to use multible tool.

Taiga I just brought up cause of knowing it works together with gitlab and is a really nice taks and issue manager ('The best™')
@sir @Wolf480pl @Michcioperz