Federati Nu: Federated N-series GNU Social
  • Login
It's "All Of Us For All Of Us" Or We're On Our Own

  • Public

    • Public
    • Groups
    • Popular
    • People

Notices tagged with dvcs

  1. LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864} (lnxw48a1@nu.federati.net)'s status on Saturday, 02-Jul-2022 14:16:35 UTC LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864} LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864}
    • clacke: looking for something 🇸🇪🇭🇰💙💛
    > We should not use github and never should have because Free Software needs Free tools[0].

    > [0] https://mako.cc/writing/hill-free_tools.html

    #GitHub's proprietariness has always been an unseen landmine, but like its predecessors #SourceForge, #GoogleCode, #CodePlex etc, projects have chosen based on present convenience (FOSS friendly, zero or low price for non-profit projects and individuals, large numbers of users --> potential for drive-by contributions). However, the big issue with GH and the others listed above was that to some degree, they were the center of gravity for code-hosting in their respective time periods.

    #DVCS software such as Git, Breezy, Mercurial, Fossil, Darcs, Pijul and so on could be used to enable a much more distributed hosting model--and should be. If people and projects do not have to join a specific #code-hosting site in order to contribute to a project / attract contributors, the allure of sites like GitHub starts to fade.

    @clacke
    In conversation about a year ago from web permalink
  2. LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864} (lnxw48a1@nu.federati.net)'s status on Sunday, 12-Jun-2022 22:25:05 UTC LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864} LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864}
    The only reason I even knew about SIT is because #Pijul and its #Nest code hosting platform was talking about embedding it in order to get shared bug-tracking built into the #DVCS.

    See https://discourse.pijul.org/t/incorporating-discussions-into-the-repo-itself/210/6
    In conversation about a year ago from Shoyu permalink

    Attachments

    1. Incorporating discussions into the repo itself
      Wiki and Issue trackers absolutely should be version controlled and ideally live near the code if for no other reason than software archaeology. That said, separation of concerns should mean how the wiki and issue tracker work should ideally be independent of the source code management system as much as possible. gh-pages branch seems to work well as a standard for wikis. Just need something human readable for issues (will org-mode take over the world?).
  3. LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864} (lnxw48a1@nu.federati.net)'s status on Tuesday, 29-Jun-2021 20:01:14 UTC LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864} LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864}
    As #Pijul approaches version 1.0, they’re working on stabilizing data and storage formats. There were a couple of changes recently, which for the first time, were mostly backwards compatible. https://pijul.org/posts/2021-06-28-two-changes/ [pijul org]

    #scm #dvcs #rust
    In conversation Tuesday, 29-Jun-2021 20:01:14 UTC from Shoyu permalink

    Attachments

    1. Pijul
      An easy to use, distributed and fast version control system.
  4. LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864} (lnxw48a1@nu.federati.net)'s status on Wednesday, 19-May-2021 03:50:07 UTC LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864} LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864}
    Not sure what "SIT":{https://sit.fyi/} does exactly. I do see a bug-tracker plugin, but nothing else.

    I came across it because there is discussion about adding bug-tracking to #Pijul ... and this was mentioned in the discussion.

    #Fossil already comes with a bug-tracker, so it is nice to see other #DVCS software starting to integrate it.
    In conversation Wednesday, 19-May-2021 03:50:07 UTC from web permalink
  5. LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864} (lnxw48a1@nu.federati.net)'s status on Monday, 17-May-2021 23:09:10 UTC LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864} LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864}
    in reply to
    • LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864}
    Correction: #Pijul ... it is a #dvcs / #scm system written in #Rust, and an evolution of some of the ideas behind #Haskell's #Darcs, including fleshing out the theoretical basis and solving a couple of major bugs.
    In conversation Monday, 17-May-2021 23:09:10 UTC from web permalink
  6. LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864} (lnxw48a1@nu.federati.net)'s status on Friday, 14-May-2021 04:08:45 UTC LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864} LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864}
    Oh, weird. The site for the #Darcs #DVCS / #SCM software is now blank.

    I can only assume an attacker defaced the site and they just relaunched it, as there is not even a front page created yet (it is a wiki).
    In conversation Friday, 14-May-2021 04:08:45 UTC from Shoyu permalink
  7. LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864} (lnxw48a1@nu.federati.net)'s status on Sunday, 07-Feb-2021 18:17:53 UTC LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864} LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864}
    in reply to
    • LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864}
    • The Tcl scripting language and related projects
    If you’re a #Rustacean / #Rustacrucian, #Deno may be interesting simply because it is written in #Rust ... by the same person who started #Node.js.

    See https://www.youtube.com/watch?v=M3BM9TB-8yA

    If you’re interested in !TclTk, then you may find #jsish interesting, because its internals are designed based on some of Tcl’s internals, and because it integrates the #Fossil #DVCS and can be updated using standard Fossil commands.
    In conversation Sunday, 07-Feb-2021 18:17:53 UTC from Shoyu permalink

    Attachments

    1. 10 Things I Regret About Node.js - Ryan Dahl - JSConf EU 2018
      By JSConf from YouTube
  8. LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864} (lnxw48a1@nu.federati.net)'s status on Monday, 30-Nov-2020 23:43:55 UTC LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864} LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864}
    https://arxiv.org/abs/1311.3903

    A Categorical Theory of Patches

    A formalization of the #Darcs theory of patches. Darcs ( http://darcs.net/ ) is a #DVCS, like #git or #hg or #Fossil, but based around patches.

    #VCS #version-control
    In conversation Monday, 30-Nov-2020 23:43:55 UTC from Shoyu permalink

    Attachments

    1. Darcs - FrontPage
    2. A Categorical Theory of Patches
      When working with distant collaborators on the same documents, one often uses a version control system, which is a program tracking the history of files and helping importing modifications brought by others as patches. The implementation of such a system requires to handle lots of situations depending on the operations performed by users on files, and it is thus difficult to ensure that all the corner cases have been correctly addressed. Here, instead of verifying the implementation of such a system, we adopt a complementary approach: we introduce a theoretical model, which is defined abstractly by the universal property that it should satisfy, and work out a concrete description of it. We begin by defining a category of files and patches, where the operation of merging the effect of two coinitial patches is defined by pushout. Since two patches can be incompatible, such a pushout does not necessarily exist in the category, which raises the question of which is the correct category to represent and manipulate files in conflicting state. We provide an answer by investigating the free completion of the category of files under finite colimits, and give an explicit description of this category: its objects are finite sets labeled by lines equipped with a transitive relation and morphisms are partial functions respecting labeling and relations.
  9. LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864} (lnxw48a1@nu.federati.net)'s status on Tuesday, 10-Nov-2020 06:03:32 UTC LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864} LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864}
    There's another #code-hosting option: #Heptapod is a fork of #GitLab that supports #Hg repos. I see a hosted version at https://about.heptapod.host/

    #VCS #DVCS #SCM
    In conversation Tuesday, 10-Nov-2020 06:03:32 UTC from mustard permalink

    Attachments

    1. Heptapod Hosting | Mercurial forge
      Host your Mercurial repositories with Heptapod and Clever Cloud
  10. LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864} (lnxw48a1@nu.federati.net)'s status on Monday, 09-Nov-2020 04:54:11 UTC LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864} LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864}
    • Federati Networks
    I think y’all know I favor the #Fossil #SCM / #DVCS over #Git (though I’m giving #Mercurial ( #Hg ) another look as well. I’m resource-constrained as well as energy-limited, but I have been thinking of standing up a miniature software forge for !FNetworks projects and users, likely using Kallithea (which can use both Hg and Git) and also having some Fossil repos (but not as part of a forge).
    In conversation Monday, 09-Nov-2020 04:54:11 UTC from Shoyu permalink

Feeds

  • Activity Streams
  • RSS 1.0
  • RSS 2.0
  • Atom
  • Help
  • About
  • FAQ
  • TOS
  • Privacy
  • Source
  • Version
  • Contact

Federati Nu: Federated N-series GNU Social is a social network, courtesy of Federati Networks. It runs on GNU social, version 2.0.0-dev, available under the GNU Affero General Public License.

Creative Commons Attribution 3.0 All Federati Nu: Federated N-series GNU Social content and data are available under the Creative Commons Attribution 3.0 license.

Switch to mobile site layout.