Hello,

The github repo [1] is now referenced as "Mirror of
Apache NiFi Flow Design System".

-Scott

[1] https://github.com/apache/nifi-fds

On Tue, May 29, 2018 at 12:31 PM, Scott Aslan <[email protected]> wrote:

> I have submitted this to INFRA: https://issues.apache.
> org/jira/browse/INFRA-16588
>
> On Mon, May 28, 2018 at 4:13 AM, Pierre Villard <
> [email protected]> wrote:
>
>> Hey guys,
>>
>> Just a minor remark: the github repo [1] is still referenced as "Mirror of
>> Apache NiFi Fluid Design System".
>> I think we should file a JIRA to INFRA to get this fixed.
>>
>> Pierre
>>
>> [1] https://github.com/apache/nifi-fds
>>
>>
>> 2018-05-25 23:36 GMT+02:00 Scott Aslan <[email protected]>:
>>
>> > Ok guys, I added a page to the nifi-site for the nifi-fds subproject:
>> > https://nifi.apache.org/fds.html
>> >
>> > -Scott
>> >
>> > On Fri, May 25, 2018 at 4:01 PM, Scott Aslan <[email protected]>
>> > wrote:
>> >
>> > > Thanks Matt!
>> > >
>> > > Andy, yes it looks like we still need to add a page to the nifi-site
>> for
>> > > this new sub project. Sorry for the broken link.
>> > >
>> > > -Scott
>> > >
>> > > On Fri, May 25, 2018 at 2:48 PM, Matt Gilman <[email protected]
>> >
>> > > wrote:
>> > >
>> > >> Scott,
>> > >>
>> > >> Thanks for offering to RM! I'm happy to help review the PR's for the
>> > >> remaining JIRA's you've identified.
>> > >>
>> > >> Matt
>> > >>
>> > >> On Fri, May 25, 2018 at 1:37 PM, Andy Christianson <
>> > >> [email protected]>
>> > >> wrote:
>> > >>
>> > >> > -----BEGIN PGP SIGNED MESSAGE-----
>> > >> > Hash: SHA1
>> > >> >
>> > >> > > Team,
>> > >> > >
>> > >> > > There has been a lot of great work done on the NiFi Flow Design
>> > System
>> > >> > [1]
>> > >> > > and although there are still a few 'in progress' issues ([3],
>> [4],
>> > >> [5])
>> > >> > I think
>> > >> > > we are probably very close to an initial release focused on a
>> > reusable
>> > >> > > platform providing a consistent set of UI/UX components across
>> the
>> > >> NiFi
>> > >> > > ecosystem.
>> > >> > >
>> > >> > > Since NiFi Registry will have a dependency on client code
>> provided
>> > by
>> > >> > the flow
>> > >> > > design system, the first release of the flow design system would
>> > need
>> > >> to
>> > >> > > occur before the next release of NiFi Registry that integrates
>> with
>> > >> it.
>> > >> > The
>> > >> > > work on the NiFi Registry side is being done as part of
>> NIFIREG-39
>> > >> [2].
>> > >> > >
>> > >> > > Let me know if anyone has any thoughts or comments.  I'm happy to
>> > act
>> > >> as
>> > >> > RM
>> > >> > > if no one else is interested in doing so, and we can start the
>> > >> process of
>> > >> > > going through JIRA to see what is left.
>> > >> > >
>> > >> > > Thanks,
>> > >> > >
>> > >> > > Scott
>> > >> > >
>> > >> > > [1] https://nifi.apache.org/fds.html
>> > >> > > [2] https://issues.apache.org/jira/browse/NIFIREG-39
>> > >> > > [3] https://issues.apache.org/jira/browse/NIFI-5219
>> > >> > > [4] https://issues.apache.org/jira/browse/NIFI-5216
>> > >> > > [5] https://issues.apache.org/jira/browse/NIFI-5240
>> > >> >
>> > >> > Glad to see the progress! FYI, the FDS link [1] appears to be
>> broken
>> > >> (404
>> > >> > Not
>> > >> > Found)
>> > >> >
>> > >> > Regards,
>> > >> >
>> > >> > Andy I.C.
>> > >> >
>> > >> > [1] https://nifi.apache.org/fds.html
>> > >> > -----BEGIN PGP SIGNATURE-----
>> > >> > Version: GnuPG v2.0.22 (GNU/Linux)
>> > >> >
>> > >> > iQEcBAEBAgAGBQJbCEm2AAoJEG1+mBKNMpIDbhEH/2UdqgAh2F7F8rvIYIqPbX53
>> > >> > Ucjk8SlCLSbmocS8vIx4SbIQamy6bEYgtdqPwUvyfm82QLUW2zDt+1WtHYVMNOlV
>> > >> > dikiNIHRR/yqPCU8ZfNkyKJI0ajw+lvc/DSmH97TYsmmYw889lX/LfnLuObq0RG1
>> > >> > pflvme1E7vDr0CFLSJ39qBnKeTL/AvVDINBXjmdDr/6LlK9Bw/XdHdkMnFZ4dpUF
>> > >> > /mHeNfp+RtHyAHP+Igw1aqaSiNyRWArQlF/T3WHhR9kpyjq+Fca+bl5OMufKxjiq
>> > >> > ATLU6UsoRbBDwmlf/ZOI+O/CKNfD+oHzKFSPpIVsxdkJHWp3huaJiuGyUlbxUhA=
>> > >> > =q33Z
>> > >> > -----END PGP SIGNATURE-----
>> > >> >
>> > >> >
>> > >> >
>> > >> > ​Sent from ProtonMail, Swiss-based encrypted email.​
>> > >> >
>> > >> >
>> > >>
>> > >
>> > >
>> >
>>
>
>

Reply via email to