Re: Standardise on 'main' as the default branch?

[Zili Chen]

+1

Sounds good to go.

On 2023/04/01 12:10:15 sebb wrote:
> All bar one of the 4 comdev Git repos use 'main' as the default branch.
> 
> I think we should standardise on that going forward, and change the
> default branch for comdev-site.
> 
> Agreed?
> 
> Sebb
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
> 
> 

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Re: Standardise on 'main' as the default branch?

[Willem Jiang]

+1 for it.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Sat, Apr 1, 2023 at 8:11 PM sebb  wrote:
>
> All bar one of the 4 comdev Git repos use 'main' as the default branch.
>
> I think we should standardise on that going forward, and change the
> default branch for comdev-site.
>
> Agreed?
>
> Sebb
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Re: Standardise on 'main' as the default branch?

[Christofer Dutz]

I would like to make a slightly different proposal.
Name the branch, on which development happens "develop" and the one that 
contains the released versions "releases". With "main" you never really know 
what it's used for.

But I think I brought this up multiple times before, so if be +1 on a change.

Chris

Gesendet von Outlook für Android

From: Willem Jiang 
Sent: Sunday, April 2, 2023 10:19:44 AM
To: dev@community.apache.org 
Subject: Re: Standardise on 'main' as the default branch?

+1 for it.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Sat, Apr 1, 2023 at 8:11 PM sebb  wrote:
>
> All bar one of the 4 comdev Git repos use 'main' as the default branch.
>
> I think we should standardise on that going forward, and change the
> default branch for comdev-site.
>
> Agreed?
>
> Sebb
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Re: Standardise on 'main' as the default branch?

[sebb]

On Sun, 2 Apr 2023 at 09:39, Christofer Dutz  wrote:
>
> I would like to make a slightly different proposal.
> Name the branch, on which development happens "develop" and the one that 
> contains the released versions "releases". With "main" you never really know 
> what it's used for.

I agree that main is no less ambiguous than master, but the website
does not really have a development/release cycle, so I'm not sure
'release' is appropriate here.

Maybe the default branch should be something like 'production' or
'live' for websites.
However that would mean changing the other repos to keep in step.

> But I think I brought this up multiple times before, so if be +1 on a change.

Thanks!

> Chris
>
> Gesendet von Outlook für Android
> 
> From: Willem Jiang 
> Sent: Sunday, April 2, 2023 10:19:44 AM
> To: dev@community.apache.org 
> Subject: Re: Standardise on 'main' as the default branch?
>
> +1 for it.
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Sat, Apr 1, 2023 at 8:11 PM sebb  wrote:
> >
> > All bar one of the 4 comdev Git repos use 'main' as the default branch.
> >
> > I think we should standardise on that going forward, and change the
> > default branch for comdev-site.
> >
> > Agreed?
> >
> > Sebb
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Re: Standardise on 'main' as the default branch?

[tison]

> Name the branch, on which development happens "develop" and the one that
contains the released versions "releases". With "main" you never really
know what it's used for.

To me, "main" is always "develop".

Best,
tison.


sebb  于2023年4月2日周日 19:34写道：

> On Sun, 2 Apr 2023 at 09:39, Christofer Dutz 
> wrote:
> >
> > I would like to make a slightly different proposal.
> > Name the branch, on which development happens "develop" and the one that
> contains the released versions "releases". With "main" you never really
> know what it's used for.
>
> I agree that main is no less ambiguous than master, but the website
> does not really have a development/release cycle, so I'm not sure
> 'release' is appropriate here.
>
> Maybe the default branch should be something like 'production' or
> 'live' for websites.
> However that would mean changing the other repos to keep in step.
>
> > But I think I brought this up multiple times before, so if be +1 on a
> change.
>
> Thanks!
>
> > Chris
> >
> > Gesendet von Outlook für Android
> > 
> > From: Willem Jiang 
> > Sent: Sunday, April 2, 2023 10:19:44 AM
> > To: dev@community.apache.org 
> > Subject: Re: Standardise on 'main' as the default branch?
> >
> > +1 for it.
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
> > On Sat, Apr 1, 2023 at 8:11 PM sebb  wrote:
> > >
> > > All bar one of the 4 comdev Git repos use 'main' as the default branch.
> > >
> > > I think we should standardise on that going forward, and change the
> > > default branch for comdev-site.
> > >
> > > Agreed?
> > >
> > > Sebb
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > > For additional commands, e-mail: dev-h...@community.apache.org
> > >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>

[GitHub] [comdev-site] rlenferink commented on pull request #100: Use pinned version of Hugo

[via GitHub]

rlenferink commented on PR #100:
URL: https://github.com/apache/comdev-site/pull/100#issuecomment-1493320573

   > > But it seems that only works for maven, jdk and gradle: 
https://www.jenkins.io/doc/book/pipeline/syntax/#supported-tools.
   > 
   > However https://www.jenkins.io/doc/book/managing/tools/ says that the 
built-in tools are: Ant, Git, JDK and Maven. This suggests that it may be 
possible to configure other tools. Unfortunately there is no documentation.
   
   The page you found seems to be more correct (checking my local Jenkins 
instance). But indeed, no documentation doesn't really help here.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

[GitHub] [comdev-site] rlenferink commented on a diff in pull request #100: Use pinned version of Hugo

[via GitHub]

rlenferink commented on code in PR #100:
URL: https://github.com/apache/comdev-site/pull/100#discussion_r1155303835


##
Jenkinsfile:
##
@@ -56,10 +68,13 @@ pipeline {
 stage('Build') {
 steps {
 script {
-sh 'for i in $(which -a hugo) ; do echo $i; $i version; 
done'
-sh 'hugo version'
-sh "hugo --destination ${env.OUT_DIR}"
-sh "${env.PAGEFIND_DIR}/bin/pagefind --source 
${env.OUT_DIR}"
+withEnv(["PATH+HUGO=${env.HUGO_DIR}/bin", 
"PATH+PAGEFIND=${env.PAGEFIND_DIR}/bin"]) {

Review Comment:
   > If for some reason the hugo executable is not present at the first item on 
the path, then the withEnv version will fall back to checking the rest of the 
path. That would not be immediately obvious unless the build failed.
   
   Good catch! With that in mind, I'll update the PR.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

[GitHub] [comdev-site] rlenferink commented on pull request #100: Use pinned version of Hugo

[via GitHub]

rlenferink commented on PR #100:
URL: https://github.com/apache/comdev-site/pull/100#issuecomment-1493328882

   @sebbASF does this look okay to you to be merged?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Re: Standardise on 'main' as the default branch?

[Craig Russell]

Yes, of course change master to main.

Craig

> On Apr 2, 2023, at 04:33, sebb  wrote:
> 
> On Sun, 2 Apr 2023 at 09:39, Christofer Dutz  
> wrote:
>> 
>> I would like to make a slightly different proposal.
>> Name the branch, on which development happens "develop" and the one that 
>> contains the released versions "releases". With "main" you never really know 
>> what it's used for.
> 
> I agree that main is no less ambiguous than master, but the website
> does not really have a development/release cycle, so I'm not sure
> 'release' is appropriate here.
> 
> Maybe the default branch should be something like 'production' or
> 'live' for websites.
> However that would mean changing the other repos to keep in step.
> 
>> But I think I brought this up multiple times before, so if be +1 on a change.
> 
> Thanks!
> 
>> Chris
>> 
>> Gesendet von Outlook für Android
>> 
>> From: Willem Jiang 
>> Sent: Sunday, April 2, 2023 10:19:44 AM
>> To: dev@community.apache.org 
>> Subject: Re: Standardise on 'main' as the default branch?
>> 
>> +1 for it.
>> 
>> Willem Jiang
>> 
>> Twitter: willemjiang
>> Weibo: 姜宁willem
>> 
>> On Sat, Apr 1, 2023 at 8:11 PM sebb  wrote:
>>> 
>>> All bar one of the 4 comdev Git repos use 'main' as the default branch.
>>> 
>>> I think we should standardise on that going forward, and change the
>>> default branch for comdev-site.
>>> 
>>> Agreed?
>>> 
>>> Sebb
>>> 
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
>>> For additional commands, e-mail: dev-h...@community.apache.org
>>> 
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
>> For additional commands, e-mail: dev-h...@community.apache.org
>> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
> 

Craig L Russell
c...@apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

AW: Standardise on 'main' as the default branch?

[Christofer Dutz]

Hi,

There are many projects, where “main” contains the latest released version and 
„develop“ is for development.
Others use “main” for development and something else for releases.

That’s why I’m suggesting naming the threads according to what they are used 
for.

“main” for a developer is probably the branch he does his most work on (aka 
“develop”).
“main” for a user is probably the branch that he uses for using the framework 
(aka “release”).

With “release” and “develop” I think it’s absolutely clear what is on which 
branch.

That was why I suggested it.

Chris


Von: tison 
Datum: Sonntag, 2. April 2023 um 14:18
An: dev@community.apache.org 
Betreff: Re: Standardise on 'main' as the default branch?
> Name the branch, on which development happens "develop" and the one that
contains the released versions "releases". With "main" you never really
know what it's used for.

To me, "main" is always "develop".

Best,
tison.


sebb  于2023年4月2日周日 19:34写道：

> On Sun, 2 Apr 2023 at 09:39, Christofer Dutz 
> wrote:
> >
> > I would like to make a slightly different proposal.
> > Name the branch, on which development happens "develop" and the one that
> contains the released versions "releases". With "main" you never really
> know what it's used for.
>
> I agree that main is no less ambiguous than master, but the website
> does not really have a development/release cycle, so I'm not sure
> 'release' is appropriate here.
>
> Maybe the default branch should be something like 'production' or
> 'live' for websites.
> However that would mean changing the other repos to keep in step.
>
> > But I think I brought this up multiple times before, so if be +1 on a
> change.
>
> Thanks!
>
> > Chris
> >
> > Gesendet von Outlook für Android
> > 
> > From: Willem Jiang 
> > Sent: Sunday, April 2, 2023 10:19:44 AM
> > To: dev@community.apache.org 
> > Subject: Re: Standardise on 'main' as the default branch?
> >
> > +1 for it.
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
> > On Sat, Apr 1, 2023 at 8:11 PM sebb  wrote:
> > >
> > > All bar one of the 4 comdev Git repos use 'main' as the default branch.
> > >
> > > I think we should standardise on that going forward, and change the
> > > default branch for comdev-site.
> > >
> > > Agreed?
> > >
> > > Sebb
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > > For additional commands, e-mail: dev-h...@community.apache.org
> > >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>

[GitHub] [comdev-site] sebbASF commented on pull request #100: Use pinned version of Hugo

[via GitHub]

sebbASF commented on PR #100:
URL: https://github.com/apache/comdev-site/pull/100#issuecomment-1493379962

   The env.HUGO and env.PAGEFIND variables are redundant, in my view, given 
that they are only used once


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Re: Standardise on 'main' as the default branch?

[sebb]

On Sun, 2 Apr 2023 at 16:06, Christofer Dutz  wrote:
>
> Hi,
>
> There are many projects, where “main” contains the latest released version 
> and „develop“ is for development.
> Others use “main” for development and something else for releases.
>
> That’s why I’m suggesting naming the threads according to what they are used 
> for.
>
> “main” for a developer is probably the branch he does his most work on (aka 
> “develop”).
> “main” for a user is probably the branch that he uses for using the framework 
> (aka “release”).
>
> With “release” and “develop” I think it’s absolutely clear what is on which 
> branch.

That is perhaps true for a code repo, though it's unlikely that there
will be a single develop branch.

Not sure they makes sense for a website repo.

> That was why I suggested it.
>
> Chris
>
>
> Von: tison 
> Datum: Sonntag, 2. April 2023 um 14:18
> An: dev@community.apache.org 
> Betreff: Re: Standardise on 'main' as the default branch?
> > Name the branch, on which development happens "develop" and the one that
> contains the released versions "releases". With "main" you never really
> know what it's used for.
>
> To me, "main" is always "develop".
>
> Best,
> tison.
>
>
> sebb  于2023年4月2日周日 19:34写道：
>
> > On Sun, 2 Apr 2023 at 09:39, Christofer Dutz 
> > wrote:
> > >
> > > I would like to make a slightly different proposal.
> > > Name the branch, on which development happens "develop" and the one that
> > contains the released versions "releases". With "main" you never really
> > know what it's used for.
> >
> > I agree that main is no less ambiguous than master, but the website
> > does not really have a development/release cycle, so I'm not sure
> > 'release' is appropriate here.
> >
> > Maybe the default branch should be something like 'production' or
> > 'live' for websites.
> > However that would mean changing the other repos to keep in step.
> >
> > > But I think I brought this up multiple times before, so if be +1 on a
> > change.
> >
> > Thanks!
> >
> > > Chris
> > >
> > > Gesendet von Outlook für Android
> > > 
> > > From: Willem Jiang 
> > > Sent: Sunday, April 2, 2023 10:19:44 AM
> > > To: dev@community.apache.org 
> > > Subject: Re: Standardise on 'main' as the default branch?
> > >
> > > +1 for it.
> > >
> > > Willem Jiang
> > >
> > > Twitter: willemjiang
> > > Weibo: 姜宁willem
> > >
> > > On Sat, Apr 1, 2023 at 8:11 PM sebb  wrote:
> > > >
> > > > All bar one of the 4 comdev Git repos use 'main' as the default branch.
> > > >
> > > > I think we should standardise on that going forward, and change the
> > > > default branch for comdev-site.
> > > >
> > > > Agreed?
> > > >
> > > > Sebb
> > > >
> > > > -
> > > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > > > For additional commands, e-mail: dev-h...@community.apache.org
> > > >
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > > For additional commands, e-mail: dev-h...@community.apache.org
> > >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
> >
> >

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Re: Standardise on 'main' as the default branch?

[Gary Gregory]

I like release and develop. FWIW, a lot of Apache Commons components use
release already.

Gary

On Sun, Apr 2, 2023, 11:06 Christofer Dutz 
wrote:

> Hi,
>
> There are many projects, where “main” contains the latest released version
> and „develop“ is for development.
> Others use “main” for development and something else for releases.
>
> That’s why I’m suggesting naming the threads according to what they are
> used for.
>
> “main” for a developer is probably the branch he does his most work on
> (aka “develop”).
> “main” for a user is probably the branch that he uses for using the
> framework (aka “release”).
>
> With “release” and “develop” I think it’s absolutely clear what is on
> which branch.
>
> That was why I suggested it.
>
> Chris
>
>
> Von: tison 
> Datum: Sonntag, 2. April 2023 um 14:18
> An: dev@community.apache.org 
> Betreff: Re: Standardise on 'main' as the default branch?
> > Name the branch, on which development happens "develop" and the one that
> contains the released versions "releases". With "main" you never really
> know what it's used for.
>
> To me, "main" is always "develop".
>
> Best,
> tison.
>
>
> sebb  于2023年4月2日周日 19:34写道：
>
> > On Sun, 2 Apr 2023 at 09:39, Christofer Dutz 
> > wrote:
> > >
> > > I would like to make a slightly different proposal.
> > > Name the branch, on which development happens "develop" and the one
> that
> > contains the released versions "releases". With "main" you never really
> > know what it's used for.
> >
> > I agree that main is no less ambiguous than master, but the website
> > does not really have a development/release cycle, so I'm not sure
> > 'release' is appropriate here.
> >
> > Maybe the default branch should be something like 'production' or
> > 'live' for websites.
> > However that would mean changing the other repos to keep in step.
> >
> > > But I think I brought this up multiple times before, so if be +1 on a
> > change.
> >
> > Thanks!
> >
> > > Chris
> > >
> > > Gesendet von Outlook für Android
> > > 
> > > From: Willem Jiang 
> > > Sent: Sunday, April 2, 2023 10:19:44 AM
> > > To: dev@community.apache.org 
> > > Subject: Re: Standardise on 'main' as the default branch?
> > >
> > > +1 for it.
> > >
> > > Willem Jiang
> > >
> > > Twitter: willemjiang
> > > Weibo: 姜宁willem
> > >
> > > On Sat, Apr 1, 2023 at 8:11 PM sebb  wrote:
> > > >
> > > > All bar one of the 4 comdev Git repos use 'main' as the default
> branch.
> > > >
> > > > I think we should standardise on that going forward, and change the
> > > > default branch for comdev-site.
> > > >
> > > > Agreed?
> > > >
> > > > Sebb
> > > >
> > > > -
> > > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > > > For additional commands, e-mail: dev-h...@community.apache.org
> > > >
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > > For additional commands, e-mail: dev-h...@community.apache.org
> > >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
> >
> >
>

Re: Standardise on 'main' as the default branch?

[Jarek Potiuk]

I think it's really a matter of project's choice.

Those who use gitflow use main(master)/release/develop - they have
all well-defined meaning and it's cool for projects using it. For other
projects, main might be the default development choice if their
merge/release workflow is simpler (that's airflow's choice for example -
even if it is a code repo, this works well for us too). I personally adapt
to whatever style project uses and don't prefer one over the other -
whatever is comfortable for most of the people contributing there is cool.
This is what I love about git that it does not make opinionated choices and
every project can choose their workflow.

J

On Sun, Apr 2, 2023 at 7:20 PM Gary Gregory  wrote:

> I like release and develop. FWIW, a lot of Apache Commons components use
> release already.
>
> Gary
>
> On Sun, Apr 2, 2023, 11:06 Christofer Dutz 
> wrote:
>
> > Hi,
> >
> > There are many projects, where “main” contains the latest released
> version
> > and „develop“ is for development.
> > Others use “main” for development and something else for releases.
> >
> > That’s why I’m suggesting naming the threads according to what they are
> > used for.
> >
> > “main” for a developer is probably the branch he does his most work on
> > (aka “develop”).
> > “main” for a user is probably the branch that he uses for using the
> > framework (aka “release”).
> >
> > With “release” and “develop” I think it’s absolutely clear what is on
> > which branch.
> >
> > That was why I suggested it.
> >
> > Chris
> >
> >
> > Von: tison 
> > Datum: Sonntag, 2. April 2023 um 14:18
> > An: dev@community.apache.org 
> > Betreff: Re: Standardise on 'main' as the default branch?
> > > Name the branch, on which development happens "develop" and the one
> that
> > contains the released versions "releases". With "main" you never really
> > know what it's used for.
> >
> > To me, "main" is always "develop".
> >
> > Best,
> > tison.
> >
> >
> > sebb  于2023年4月2日周日 19:34写道：
> >
> > > On Sun, 2 Apr 2023 at 09:39, Christofer Dutz <
> christofer.d...@c-ware.de>
> > > wrote:
> > > >
> > > > I would like to make a slightly different proposal.
> > > > Name the branch, on which development happens "develop" and the one
> > that
> > > contains the released versions "releases". With "main" you never really
> > > know what it's used for.
> > >
> > > I agree that main is no less ambiguous than master, but the website
> > > does not really have a development/release cycle, so I'm not sure
> > > 'release' is appropriate here.
> > >
> > > Maybe the default branch should be something like 'production' or
> > > 'live' for websites.
> > > However that would mean changing the other repos to keep in step.
> > >
> > > > But I think I brought this up multiple times before, so if be +1 on a
> > > change.
> > >
> > > Thanks!
> > >
> > > > Chris
> > > >
> > > > Gesendet von Outlook für Android
> > > > 
> > > > From: Willem Jiang 
> > > > Sent: Sunday, April 2, 2023 10:19:44 AM
> > > > To: dev@community.apache.org 
> > > > Subject: Re: Standardise on 'main' as the default branch?
> > > >
> > > > +1 for it.
> > > >
> > > > Willem Jiang
> > > >
> > > > Twitter: willemjiang
> > > > Weibo: 姜宁willem
> > > >
> > > > On Sat, Apr 1, 2023 at 8:11 PM sebb  wrote:
> > > > >
> > > > > All bar one of the 4 comdev Git repos use 'main' as the default
> > branch.
> > > > >
> > > > > I think we should standardise on that going forward, and change the
> > > > > default branch for comdev-site.
> > > > >
> > > > > Agreed?
> > > > >
> > > > > Sebb
> > > > >
> > > > >
> -
> > > > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > > > > For additional commands, e-mail: dev-h...@community.apache.org
> > > > >
> > > >
> > > > -
> > > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > > > For additional commands, e-mail: dev-h...@community.apache.org
> > > >
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > > For additional commands, e-mail: dev-h...@community.apache.org
> > >
> > >
> >
>

regarding update common skin bootstrap.

[Rashi arora]

hello,

i am writing a Gsoc proposal to contribute for update common skin bootstrap.

after going through the Jira ticket i came to the conclusion:-

1)the common skin is majorly related to fluido
2)usage of doxia sidetool and jbake can fasten the process
3)Making all relevant changes in a separate stylesheet for all maven skins
and later adding the css components to the xml's of respective common
skin.(it will involve usage of creating a new theme that involves Bootstrap
and java plugins.

optional:using figma'css for some parts(like using Jbake)and then later
combining it to the backend java.

All code will thoroughly documented to ensure it is easy to maintain and
modify in the future,also testing will be done to ensure it meet's maven
skin's requirements.

will sincerely wait for your response.
Thanking you,
Rashi.

update common skin bootstrap.

[Rashi arora]

hello,

i am writing a Gsoc proposal to contribute for update common skin bootstrap.

after going through the Jira ticket i came to the conclusion:-

1)the common skin is majorly related to fluido
2)usage of doxia sidetool and jbake can fasten the process
3)Making all relevant changes in a separate stylesheet for all maven skins
and later adding the css components to the xml's of respective common
skin.(it will involve usage of creating a new theme that involves Bootstrap
and java plugins.

optional:using figma'css for some parts(like using Jbake)and then later
combining it to the backend java.

All code will thoroughly documented to ensure it is easy to maintain and
modify in the future,also testing will be done to ensure it meet's maven
skin's requirements.

will sincerely wait for your response.
Thanking you,
Rashi.

[GitHub] [comdev-events-site] sebbASF commented on pull request #4: Obsolete

[via GitHub]

sebbASF commented on PR #4:
URL: https://github.com/apache/comdev-events-site/pull/4#issuecomment-1493461512

   Please see https://community-test.staged.apache.org/ which shows the result 
of applying PR #4 and PR #3


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

[GitHub] [comdev-events-site] sebbASF commented on pull request #3: Add pagefind

[via GitHub]

sebbASF commented on PR #3:
URL: https://github.com/apache/comdev-events-site/pull/3#issuecomment-1493461566

   Please see https://community-test.staged.apache.org/ which shows the result 
of applying PR #4 and PR #3


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org