public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mikael Morin <morin-mikael@orange.fr>
To: Andre Vehreschild <vehre@gmx.de>
Cc: Damian Rouson <damian@archaeologic.codes>,
	Thomas Koenig <tkoenig@netcologne.de>,
	Benson Muite <benson_muite@emailplus.org>,
	Jerry D <jvdelisle2@gmail.com>,
	Paul Richard Thomas <paul.richard.thomas@gmail.com>,
	GCC-Fortran-ML <fortran@gcc.gnu.org>,
	Lexi Pimenidis <lexi@badgersystems.de>
Subject: Re: Possible funding of gfortran work
Date: Mon, 5 Jun 2023 13:44:52 +0200	[thread overview]
Message-ID: <d2152b84-1302-79ed-c759-0c5b3849039a@orange.fr> (raw)
In-Reply-To: <20230605100825.78c4ac78@vepi2>

Le 05/06/2023 à 10:08, Andre Vehreschild a écrit :
>> Regarding the time estimates, it's a bit difficult as we can't foresee
>> at this stage the amount of regressions that will need to be fixed, and
>> how difficult they will be.  I'm not even sure that the process of
>> picking one regression and fixing it will eventually converge to a
>> zero-regression state.  It doesn't mean much, but I expect to spend
>> between 3 and 6 months on every item I have proposed.  But I expected
>> those items to be discussed, prioritized, and either acknowledged or
>> refused by the contributors before.
> 
> You mean, you will 3 to 6 month full-time for the scalarizer rework, the API
> thingys and so on? Or is the estimate on how long it will take you to do the
> things in total, i.e. not working full-time on them?
> 
The latter, 3-6 months delivery time each item at 60% working time.

> I am asking that specifically because we need to estimate the person days they
> pay for and time boundary up to when the project will be done.
> 
Yes, I don't like it but I understand the need for estimating.
I have looked at the evaluation criteria at [1]. There is among other 
things:
> Furthermore, we look at how well the planning for the project is laid out. Are the activities well-structured, appropriate and feasible?

I think we are far from having a "well laid out planning".  Even if it's 
difficult to estimate the amount of days of work, we should probably at 
least try to decompose the project into milestones, that is (small) 
steps proving progress toward the target.

[1] https://sovereigntechfund.de/en/applications/



  reply	other threads:[~2023-06-05 11:45 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-26  4:34 Jerry DeLisle
2023-05-26 17:09 ` Bernhard Reutner-Fischer
2023-05-26 21:22 ` Jerry D
2023-05-27  8:08   ` Thomas Koenig
2023-05-27 11:24     ` Andre Vehreschild
2023-05-27 16:19       ` Paul Richard Thomas
2023-05-28 14:26         ` Nicolas König
2023-05-28 15:07         ` Thomas Koenig
2023-05-28 19:25         ` Mikael Morin
2023-05-28 20:53           ` Jerry D
2023-05-30 13:32             ` Andre Vehreschild
2023-05-30 20:08               ` Thomas Koenig
2023-05-31  3:46                 ` Benson Muite
2023-05-31  6:08                   ` Thomas Koenig
2023-05-31  8:42                     ` Benson Muite
2023-05-31 12:23                     ` Andre Vehreschild
2023-05-31 14:08                       ` Damian Rouson
2023-06-01  9:18                         ` Andre Vehreschild
2023-06-01 10:56                           ` Bernhard Reutner-Fischer
2023-06-01 10:59                           ` Mikael Morin
2023-06-04  8:23                             ` Thomas Koenig
2023-06-05  8:08                             ` Andre Vehreschild
2023-06-05 11:44                               ` Mikael Morin [this message]
2023-06-06 13:06                                 ` Andre Vehreschild
2023-06-08 12:38                                   ` Mikael Morin
2023-06-14  8:28                                     ` Andre Vehreschild
2023-06-14  9:40                                       ` Mikael Morin
2023-06-14 18:48                                         ` Bernhard Reutner-Fischer
2023-06-01 11:12                           ` Benson Muite
2023-06-04  7:49                             ` Thomas Koenig
2023-06-05 10:12                               ` Andre Vehreschild
2023-06-05 10:07                             ` Andre Vehreschild
2023-06-05 12:16                               ` Thomas Koenig
2023-06-05 12:21                                 ` Andre Vehreschild
2023-06-08  5:34                               ` Benson Muite
2023-06-14  8:00                                 ` Andre Vehreschild
2023-06-02  0:53                           ` Jerry D
2023-06-05 10:09                             ` Andre Vehreschild

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d2152b84-1302-79ed-c759-0c5b3849039a@orange.fr \
    --to=morin-mikael@orange.fr \
    --cc=benson_muite@emailplus.org \
    --cc=damian@archaeologic.codes \
    --cc=fortran@gcc.gnu.org \
    --cc=jvdelisle2@gmail.com \
    --cc=lexi@badgersystems.de \
    --cc=paul.richard.thomas@gmail.com \
    --cc=tkoenig@netcologne.de \
    --cc=vehre@gmx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).