[prev in list] [next in list] [prev in thread] [next in thread]
List: jedit-users
Subject: Re: [ jEdit-users ] modernizing the build process: github/actions, maven central, etc.
From: "Matthieu Casanova" <chocolat.mou () gmail ! com>
Date: 2023-09-16 20:15:05
Message-ID: e9cf1309-bd24-42bc-bb4c-90c756c7b7c7 () app ! fastmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Hey,
about github vs Sourceforge I must say that I use Github a lot for various projects \
and I find it is much more fluid to work with it than Sourceforge which failed to \
evolve. But in any case before making such move the first thing to do would be to \
migrate to git which would be very nice but is also a time consuming task.
--
Matthieu Casanova
chocolat.mou@gmail.com
Lun 12 juin 2023, à 11:44, Vampire a écrit :
> Hi again
>
> Forgot to say, whether we "move" to GitHub or just mirror the code is a completely \
> different discussion. While many projects went away from SourceForge, this is not \
> really mandatory. SourceForge is not dead to my knowledge and also provides much \
> more possibilities and flexibility. For example, for the things already in Git \
> repositories we have our own Git hooks running on the SourceForge repos that are \
> not possible on GitHub and so on.
> Regards
> Björn
>
> Am Mo., 12. Juni 2023 um 11:41 Uhr schrieb Vampire <Vampire@jedit.org>:
> > Hi David
> >
> > I know I horribly failed in doing the Git-migration in a timely manner,
> > but I'm going to soon pick up where I left off and finally finish the Git \
> > migration of the source code, I was just unfortunately interrupted again by some \
> > paid work. :-(
> > There is no need for the `jedit-project` org on GitHub you just invited me to \
> > though. We already have `jedit-editor` on GitHub, `jedit` group on GitLab, and \
> > the `jEdit` workspace on Bitbucket, and I'm still hoping to get contact to the \
> > seemingly unused `jedit` account on GitHub to also there get the name.
> > Once I finished the Git-migration of the main repo and also the plugins, I would \
> > at least put some mirroring up to have the code also on GitHub and maybe the \
> > others. And I'm also planning to then use GitHub actions for building, especially \
> > as you can build on macOS for free which we need for building the macOS \
> > distributable. Actually I'm already "abusing" one of my other GitHub projects' \
> > GitHub actions to do the macOS build on releases, so I know it works as intended. \
> > Best regards
> > Björn
> >
> >
> > Am Mo., 12. Juni 2023 um 11:07 Uhr schrieb David Ankin <daveankin+jedit@gmail.com \
> > <mailto:daveankin%2Bjedit@gmail.com>>:
> > > Hi folks,
> > >
> > > I would like to create an official home for this project on github, resume \
> > > publishing versions of the library (or reusable pieces?) to maven central - i \
> > > believe this would be beneficial to both users and developers as it would \
> > > encourage people to view the project as living rather than dead and \
> > > unmaintained. its sort of an inevitable association with source forge.
> > > if anyone is interested in making this a reality, let me know.
> > >
> > > best,
> > > David
> > > --
> > > -----------------------------------------------
> > > jEdit Users' List
> > > jEdit-users@lists.sourceforge.net
> > > https://lists.sourceforge.net/lists/listinfo/jedit-users
>
> --
> -----------------------------------------------
> jEdit Users' List
> jEdit-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/jedit-users
>
[Attachment #5 (text/html)]
<!DOCTYPE html><html><head><title></title><style \
type="text/css">p.MsoNormal,p.MsoNoSpacing{margin:0}</style></head><body><div \
style="font-family:Arial;">Hey,<br></div><div style="font-family:Arial;">about github \
vs Sourceforge I must say that I use Github a lot for various projects and I find it \
is much more fluid to work with it than Sourceforge which failed to \
evolve.<br></div><div style="font-family:Arial;">But in any case before making such \
move the first thing to do would be to migrate to git which would be very nice but is \
also a time consuming task.</div><div style="font-family:Arial;"><br></div><div \
id="sig19919457"><div class="signature">-- <br></div><div \
class="signature"> Matthieu Casanova<br></div><div \
class="signature"> <a \
href="mailto:chocolat.mou@gmail.com">chocolat.mou@gmail.com</a><br></div><div \
class="signature"><br></div></div><div style="font-family:Arial;"><br></div><div>Lun \
12 juin 2023, à 11:44, Vampire a écrit :<br></div><blockquote type="cite" id="qt" \
style=""><div dir="ltr"><div>Hi again<br></div><div><br></div><div>Forgot to say, \
whether we "move" to GitHub or just mirror the code is a completely different \
discussion.<br></div><div>While many projects went away from SourceForge, this is not \
really mandatory.<br></div><div>SourceForge is not dead to my knowledge and also \
provides much more possibilities and flexibility.<br></div><div>For example, for the \
things already in Git repositories we have our own Git hooks running on the \
SourceForge repos that are not possible on GitHub and so \
on.<br></div><div><br></div><div>Regards<br></div><div>Björn<br></div></div><div><br></div><div \
class="qt-gmail_quote"><div dir="ltr" class="qt-gmail_attr">Am Mo., 12. Juni 2023 um \
11:41 Uhr schrieb Vampire <<a \
href="mailto:Vampire@jedit.org">Vampire@jedit.org</a>>:<br></div><blockquote \
class="qt-gmail_quote" \
style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204, \
204, 204);padding-left:1ex;"><div dir="ltr"><div>Hi \
David<br></div><div><br></div><div>I know I horribly failed in doing the \
Git-migration in a timely manner,<br></div><div>but I'm going to soon pick up where I \
left off and finally finish the Git migration of the source code,<br></div><div>I was \
just unfortunately interrupted again by some paid work. \
:-(<br></div><div><br></div><div>There is no need for the `jedit-project` org on \
GitHub you just invited me to though.<br></div><div>We already have `jedit-editor` on \
GitHub, `jedit` group on GitLab, and the `jEdit` workspace on \
Bitbucket,<br></div><div>and I'm still hoping to get contact to the seemingly unused \
`jedit` account on GitHub to also there get the \
name.<br></div><div><br></div><div>Once I finished the Git-migration of the main repo \
and also the plugins, I would at least put some mirroring up to have the code also on \
GitHub and maybe the others.<br></div><div>And I'm also planning to then use GitHub \
actions for building, especially as you can build on macOS for free which we need for \
building the macOS distributable.<br></div><div>Actually I'm already "abusing" one of \
my other GitHub projects' GitHub actions to do the macOS build on releases, so I know \
it works as intended.<br></div><div><br></div><div>Best \
regards<br></div><div>Björn<br></div><div><br></div></div><div><br></div><div \
class="qt-gmail_quote"><div dir="ltr" class="qt-gmail_attr">Am Mo., 12. Juni 2023 um \
11:07 Uhr schrieb David Ankin <<a href="mailto:daveankin%2Bjedit@gmail.com" \
target="_blank">daveankin+jedit@gmail.com</a>>:<br></div><blockquote \
class="qt-gmail_quote" \
style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204, \
204, 204);padding-left:1ex;"><div dir="ltr"><div class="qt-gmail_quote"><div \
dir="ltr" class="qt-gmail_attr">Hi folks,<br></div><div \
dir="ltr"><div><br></div><div>I would like to create an official home for this \
project on github, resume publishing versions of the library (or reusable pieces?) to \
maven central - i believe this would be beneficial to both users and developers \
as it would encourage people to view the project as living rather than dead and \
unmaintained. its sort of an inevitable association with source \
forge.<br></div><div><br></div><div>if anyone is interested in making this a reality, \
let me know.<br></div><div><br></div><div>best,<br></div><div>David<br></div></div></div></div><div>-- \
<br></div><div> -----------------------------------------------<br></div><div> jEdit \
Users' List<br></div><div> <a href="mailto:jEdit-users@lists.sourceforge.net" \
target="_blank">jEdit-users@lists.sourceforge.net</a><br></div><div> <a \
href="https://lists.sourceforge.net/lists/listinfo/jedit-users" rel="noreferrer" \
target="_blank">https://lists.sourceforge.net/lists/listinfo/jedit-users</a><br></div> \
</blockquote></div></blockquote></div><div><br></div><div>-- <br></div><div>-----------------------------------------------<br></div><div>jEdit \
Users' List<br></div><div><a \
href="mailto:jEdit-users@lists.sourceforge.net">jEdit-users@lists.sourceforge.net</a><br></div><div><a \
href="https://lists.sourceforge.net/lists/listinfo/jedit-users">https://lists.sourceforge.net/lists/listinfo/jedit-users</a><br></div><div><br></div></blockquote><div \
style="font-family:Arial;"><br></div></body></html>
--
-----------------------------------------------
jEdit Users' List
jEdit-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jedit-users
[prev in list] [next in list] [prev in thread] [next in thread]