Re: [Savannah-hackers-public] Final-stage work/changes on adding the Git homepage source code web browsing option.

[Ian Kelling]

Ineiev <ineiev@gnu.org> writes:

> [[PGP Signed Part:Undecided]]
> On Tue, Jan 16, 2024 at 02:46:49PM -0500, Ian Kelling wrote:
>> Ineiev <ineiev@gnu.org> writes:
>>
>> > The group will use no more than one VCS for its homepage; a new
>> > field 'url_git_viewcvs_homepage' will only add unneeded complexity.
>>
>> Ayushman didn't explain some of the ideas behind this. I believe we
>> actually want projects to be able to have CVS and Git homepage
>> repositories simultaneously on the savannah side, and then be able to
>> choose and switch back and forth between which one is the source of the
>> actually published homepage.
>
> Still it will be single repository at the same time, and in fact,
> non-default values are (and will be) effectively never used.

What do you mean by "single repository at the same time"? The primarily
for the use case we envision is of existing projects moving their
webpage projects to git. That is not a default, but I think it will get
used. Anyways, I'm not sure what you are getting at.

>
> There is no need for this new field, and for any other new fields,
> on the other hand, the harm would be more than palpable.

Well, I can think of ways to reuse existing fields in new ways, or
compute information without using a field, but this seems to follow the
existing pattern in the code base: clearly fields were added when git
support was added for non-web repositories. What is the harm you see? Do
you suggest alternatives?

>
> It's much easier to workaround such things at the design stage
> than fixing them after they are built in the package.

Yes, of course. That is why we are talking. The design is flexible right
now.